Build Rdo Train in RHEL 8 on LinuxONE
by Shi Lin Huang
Hi,
Last week I asked RDO related question in CentOS-devel mail list, you
can see the question from bottom link [1]. Thanks for Alfredo kindly
help.
After we do some POC to build packages in link [2] , I still have some
questions:
1. We want contribute to RDO community, let RDO add s390x architecture
build. As there is no CentOS s390x architecture build in CentOS
repositories, we can only build and test RDO packages in RHEL, Is it
possiable we add RDO s390x build without CentOS s390x architecture
build? Build CentOS might need much more effort and time.
2. I'm trying building RDO Train packages in [2] in RHEL 8 on LinuxONE,
seems there are some package missing, such as python-d2to1. Should I
switch to build RDO Train in RHEL 7 as the start step, wait until RDO
train for CentOS 8 is ready?
3. For RDO Train on RHEL 8, can I expect python 3 is the default Python
interpreter for all OpenStack packages and dependecy packages?
Thank you.
[1]
https://lists.centos.org/pipermail/centos-devel/2019-October/017948.html
[2] https://trunk.rdoproject.org/rhel8-master/
--
Shi Lin, Huang
shilinh(a)cn.ibm.com
IBM China Systems Lab, Beijing, China
4 years, 9 months
[Meeting] RDO meeting (2019-11-27) minutes
by Javier Pena
==============================
#rdo: RDO meeting - 2019-11-27
==============================
Meeting started by jpena at 15:00:24 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_11_27/2019/rdo...
.
Meeting summary
---------------
* roll call (jpena, 15:00:45)
* CentOS8 Updates, still no ETA for centos8 buildroot in CBS. (jpena,
15:04:09)
* projects started removing support for python2 (amoralej, 15:05:02)
* Started deps bootstrap in copr
https://copr.fedorainfracloud.org/coprs/g/openstack-sig/centos8-deps
(amoralej, 15:06:26)
* deps bootstrap is using latest fedora builds in f32 and enabling
automatic dependencies in python to match fedora behavior
(amoralej, 15:07:17)
* Meeting time update (jpena, 15:10:13)
* AGREED: Meeting time moves to 14:00 UTC on Wednesdays (1 hour
earlier than before) (jpena, 15:17:02)
* Questions about RDO CI/Software Factory (jpena, 15:17:23)
* Chair for next meeting (jpena, 15:30:28)
* ACTION: leanderthal to chair the next meeting (jpena, 15:31:17)
* open floor (jpena, 15:31:36)
Meeting ended at 15:43:34 UTC.
Action items, by person
-----------------------
* leanderthal
* leanderthal to chair the next meeting
People present (lines said)
---------------------------
* jpena (41)
* leanderthal (28)
* tosky (20)
* amoralej (20)
* openstack (6)
* rdogerrit (3)
* jcapitao (2)
* tristanC (1)
Generated by `MeetBot`_ 0.1.4
5 years, 1 month
Proposal to change RDO meeting time
by Javier Pena
Hi,
Yesterday, during the weekly RDO meeting, we discussed the current schedule. During the winter time, there are collisions with the schedule of some community members, and it is also quite late for some of us.
So, I'd like to propose a change in the meeting time, to start 1 hour later than it does now: Thursdays, 14:00 UTC time. That is 15:00 CET, 19:30 IST, 9:00 EST.
If the new time works for you, please let us know. Otherwise, we will keep the current meeting time.
Regards,
Javier
5 years, 1 month
[Ask OpenStack] 7 updates about "nova", "heat", "personality", "nested", "keypair" and more
by Rain Leander
Ask OpenStack has these updates, please have a look:
- OpenStack API versus VNFM
<https://ask.openstack.org/en/question/125184/openstack-api-versus-vnfm/?s...>
(new
question)
- What is date/time format of Openstack instance log
<https://ask.openstack.org/en/question/125182/what-is-datetime-format-of-o...>
(1
rev)
- Can not create keypair with local public key
<https://ask.openstack.org/en/question/125174/can-not-create-keypair-with-...>
(new
question, 1 ans, 2 ans rev)
- How do i get IDs of the nested resources in ResourceGroup ?
<https://ask.openstack.org/en/question/125172/how-do-i-get-ids-of-the-nest...>
(new
question)
- personality - Config_drive - files size too big
<https://ask.openstack.org/en/question/110728/personality-config_drive-fil...>
(new
question, 1 ans, 1 ans rev)
- Is it possible to do comma_delimited_list inside a
comma_delimited_list ?
<https://ask.openstack.org/en/question/125169/is-it-possible-to-do-comma_d...>
(new
question)
- Using a Packstack installed Openstack to install Kubernetes
<https://ask.openstack.org/en/question/125162/using-a-packstack-installed-...>
(2
rev)
And, as always, thanks so much for being a part of the RDO Community!
--
K Rain Leander
OpenStack Community Liaison
Open Source Program Office
https://www.rdoproject.org/
http://community.redhat.com
5 years, 1 month
[rdo-users] [Meeting] RDO meeting (2019-11-20) minutes
by Joel Capitao
==============================
#rdo: RDO meeting - 2019-11-20
==============================
Meeting started by jcapitao at 15:00:54 UTC. The full logs are
available athttp://eavesdrop.openstack.org/meetings/rdo_meeting___2019_11_20/2019/r...
.
Meeting summary
---------------
* roll call (jcapitao, 15:01:11)
* CentOS8 Updates (jcapitao, 15:16:24)
* RDO legacy zuul jobs migration to native zuulv3 (jcapitao, 15:22:45)
* planning/tracking will be done with
https://review.rdoproject.org/etherpad/p/rdo-zuulv3-migration
(jcapitao, 15:23:20)
* Meeting time update (jcapitao, 15:30:15)
* ACTION: jpena to reply all to mailing list, informing proposal will
end next rdo meeting (jcapitao, 15:37:59)
* RDO Test Day Ussuri Milestone 1 (jcapitao, 15:38:20)
* RDO will be holding an RDO test day on 19 and 20 December 2019.
(jcapitao, 15:38:45)
* LINK:
https://lists.rdoproject.org/pipermail/users/2019-November/000627.html
(jcapitao, 15:39:01)
* chair for next meeting? (jcapitao, 15:43:38)
* ACTION: jpena to chair next week (jcapitao, 15:45:23)
* open floor (jcapitao, 15:46:22)
Meeting ended at 16:01:26 UTC.
Action items, by person
-----------------------
* jpena
* jpena to reply all to mailing list, informing proposal will end next
rdo meeting
* jpena to chair next week
People present (lines said)
---------------------------
* jcapitao (50)
* jpena (8)
* leanderthal (5)
* openstack (4)
* Tengu (3)
* rdogerrit (2)
* mnasiadka (2)
* rh-jelabarre (1)
Generated by `MeetBot`_ 0.1.4
5 years, 1 month
Re: [rdo-dev] dev Digest, Vol 79, Issue 10
by Akim Grudzitsky
Alan,
I added 10GB and it worked like a charm.
Thanks a lot!
On Wed, Nov 20, 2019 at 2:35 AM <dev-request(a)lists.rdoproject.org> wrote:
> Send dev mailing list submissions to
> dev(a)lists.rdoproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.rdoproject.org/mailman/listinfo/dev
> or, via email, send a message with subject or body 'help' to
> dev-request(a)lists.rdoproject.org
>
> You can reach the person managing the list at
> dev-owner(a)lists.rdoproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Packstack installation errors. (Alan Pevec)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 20 Nov 2019 08:34:55 +0100
> From: Alan Pevec <apevec(a)redhat.com>
> To: Akim Grudzitsky <akdriveus(a)gmail.com>
> Cc: RDO Developmen List <dev(a)lists.rdoproject.org>
> Subject: Re: [rdo-dev] Packstack installation errors.
> Message-ID:
> <CABYd8Scc3PEC6OkuFS6XU6Ckf+KMj=-
> quoLB_WzViHLxwZUmjA(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Akim,
>
> thanks for testing RDO, I'm CCing RDO dev list for visibility.
>
> On Wed, Nov 20, 2019 at 7:09 AM Akim Grudzitsky <akdriveus(a)gmail.com>
> wrote:
> >
> > Hi Alex and Alan,
> >
> > I attempted to install OpenStack following the Packstack installation
> steps. I was installing on the "generic/centos7" Vagrant box. I am not sure
> if this is a valid VM for the Test Day testing. But I wanted to give it a
> try. During the installation I've got the following error message:
> >
> > "
> > The installation is finished with the following error:
> > 192.168.0.40_controller.pp: [ ERROR ]
> > Applying Puppet manifests [ ERROR ]
> >
> > ERROR : Error appeared during Puppet run: 192.168.0.40_controller.pp
> > Error: Cannot allocate memory - fork(2)
>
> This looks like VM does not have enough RAM, Vagrant default seems to
> be 0.5 GB which is definitely not enough, try 8GB or more.
>
> Cheers,
> Alan
>
> > I have attached my Vagrantfile, Configuration&Installation steps, and
> the log files 192.168.0.40_controller.pp.log and openstack-setup.log
> > "
> >
> > If my test and the defect are valid, please let me know where I can log
> it.
> >
> > I also wanted to mention that I could access the OpenStack Dashboard in
> the browser http://192.168.0.40/dashboard, and authenticate using the
> password provided in the keystonerc_admin file.
> >
> > Since I am not sure if this test is valid, I decided to send you guys
> this email first. Sorry if it is not the way how it works.
> >
> > Thank you!
> >
> > Sincerely,
> > Akim
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: Vagrantfile
> Type: application/octet-stream
> Size: 132 bytes
> Desc: not available
> URL: <
> http://lists.rdoproject.org/pipermail/dev/attachments/20191120/d896fd09/a...
> >
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: Configuration&Installation_steps
> Type: application/octet-stream
> Size: 2733 bytes
> Desc: not available
> URL: <
> http://lists.rdoproject.org/pipermail/dev/attachments/20191120/d896fd09/a...
> >
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: openstack-setup.log
> Type: application/octet-stream
> Size: 7031 bytes
> Desc: not available
> URL: <
> http://lists.rdoproject.org/pipermail/dev/attachments/20191120/d896fd09/a...
> >
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: 192.168.0.40_controller.pp.log
> Type: application/octet-stream
> Size: 117174 bytes
> Desc: not available
> URL: <
> http://lists.rdoproject.org/pipermail/dev/attachments/20191120/d896fd09/a...
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> dev mailing list
> dev(a)lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/dev
>
>
> ------------------------------
>
> End of dev Digest, Vol 79, Issue 10
> ***********************************
>
5 years, 1 month
File contains no section headers.
by Akim Grudzitsky
Hello,
I followed the "How to test?" steps provided on the Ussuri Milestone1 Test
Day page (http://rdoproject.org/testday/ussuri/milestone1/).
After the $ sudo yum update -y command I've got the following error:
"File contains no section headers.file:
file:///etc/yum.repos.d/delorean-deps.repo, line: 1'<!DOCTYPE HTML PUBLIC
"-//IETF//DTD HTML 2.0//EN">\n'"
OS: CentOS 7
Is this a known error?
Thank you.
5 years, 1 month
Re: [rdo-dev] Packstack installation errors.
by Alan Pevec
Hi Akim,
thanks for testing RDO, I'm CCing RDO dev list for visibility.
On Wed, Nov 20, 2019 at 7:09 AM Akim Grudzitsky <akdriveus(a)gmail.com> wrote:
>
> Hi Alex and Alan,
>
> I attempted to install OpenStack following the Packstack installation steps. I was installing on the "generic/centos7" Vagrant box. I am not sure if this is a valid VM for the Test Day testing. But I wanted to give it a try. During the installation I've got the following error message:
>
> "
> The installation is finished with the following error:
> 192.168.0.40_controller.pp: [ ERROR ]
> Applying Puppet manifests [ ERROR ]
>
> ERROR : Error appeared during Puppet run: 192.168.0.40_controller.pp
> Error: Cannot allocate memory - fork(2)
This looks like VM does not have enough RAM, Vagrant default seems to
be 0.5 GB which is definitely not enough, try 8GB or more.
Cheers,
Alan
> I have attached my Vagrantfile, Configuration&Installation steps, and the log files 192.168.0.40_controller.pp.log and openstack-setup.log
> "
>
> If my test and the defect are valid, please let me know where I can log it.
>
> I also wanted to mention that I could access the OpenStack Dashboard in the browser http://192.168.0.40/dashboard, and authenticate using the password provided in the keystonerc_admin file.
>
> Since I am not sure if this test is valid, I decided to send you guys this email first. Sorry if it is not the way how it works.
>
> Thank you!
>
> Sincerely,
> Akim
5 years, 1 month
