[Rdo-list] CentOS 6.5 Guest image file available now
by Mike Burns
Thanks to Joey Boggs for putting this together.
A prebuilt guest-image for CentOS 6.5 has been posted to the RDO yum
repository along with the kickstart used to generate it. [1] This was
done in response to the conversation on IRC earlier.
The eventual plan would be to have this image owned and generated by the
CentOS community, perhaps as part of the Cloud SIG. This is just a
stopgap measure until the SIG is up and running.
Let us know if you find any issues with it.
Thanks
Mike
[1] http://repos.fedorapeople.org/repos/openstack/guest-images/
10 years, 9 months
[Rdo-list] CentOS Cloud Sig
by Mike Burns
We had a planning meeting to try to figure out the path forward for the
CentOS cloud sig.
Some of the highlights of the meeting:
* A single SIG that provides a number of dependencies makes sense,
possibly with variants for different projects to deliver specific
packages that apply only to them.
* Need to develop a process where certain versions are agreed upon for
common packages -- not decided yet
* Branding -- conversation is deferred to some other group/place/time
* Java packaging issues need to be worked out (doesn't impact RDO much,
but might apply to python as well)
* Discussion about whether projects would want a lot of anaconda changes
-- response was that getting content installed was sufficient and
projects would depend on things like puppet/chef/etc to configure/deploy
* What types of changes over base CentOS: java packaging, java itself,
tomcat. There is interest in other things like qemu, libvirt, etc
* Ability to work with other projects is important (Ceph, Xen, other Sigs)
Next Steps:
* figure out common ground and dependencies
* projects to nominate people who will do this work
* Sig will be primarily meritocracy. initial seeding will be based on
project nominations
* need to decide what projects will be included in the SIG
Mike
10 years, 9 months
[Rdo-list] RDO Hangouts: Suggestions/Speakers needed
by Rich Bowen
Last year we had two RDO hangouts, both on networking, and these were
very well received.
We'd like to get this started up again, with hangouts on a variety of
topics. We've had some suggestions in past threads, but nobody
volunteering to do the content.
If you're willing to speak for anywhere from 30 to 45 minutes on any
OpenStack-related topic, please let me know.
Things I'd like to see us do hangouts on include:
* Reporting/Alarming with Ceilometer
* Deploying apps with heat
* Using TryStack
* More stuff about networking, as this continues to be a common pain point
* Icehouse: What's coming
* More advanced deployments with packstack
* ...
I'd also be interested in doing one-on-one hangouts/chats on shorter
topics (10-15 minutes) if that's more your speed than a broadcast type
event.
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
10 years, 9 months
[Rdo-list] Installing Heat from RDO - dependency error
by Daniel Speichert
Hello,
I am installing Heat service according to the guide from RDO website:http://openstack.redhat.com/Deploy_Heat_and_launch_your_first_App...
All packages install fine except for the last one: openstack-heat-templates. The package it depends on is just not in any repositories (CentOS, EPEL or OpenStack Havana RDO).
Error: Package: openstack-heat-templates-0-0.1.20140106git.el6.noarch (openstack-havana)
Requires: libvirt-daemon
Does anybody know how to fix this issue?
OS: CentOS release 6.5 (Final)
REPO LIST:
repo id repo name
base CentOS-6 - Base
ceph Ceph Repos
ceph-extras Ceph Extra Packages and Backports x86_64
ceph-extras-noarch Ceph Extra Packages and Backports noarch
ceph-extras-source Ceph Extra Packages and Backports Sources
epel Extra Packages for Enterprise Linux 6 - x86_64
extras CentOS-6 - Extras
foreman Foreman stable
foreman-plugins Foreman stable - plugins
openstack-havana OpenStack Havana Repository
puppetlabs-deps Puppet Labs Dependencies El 6 - x86_64
puppetlabs-products Puppet Labs Products El 6 - x86_64
updates CentOS-6 - Updates
Thanks!
Daniel
10 years, 9 months
Re: [Rdo-list] RDO Hangouts: Suggestions/Speakers needed
by jonathan.creasy
Ceilometer is of particular interest to our organization (contegix.com). I would be very interested in diving into that.
We would be happy if someone else had the content for us to learn from or if no such person exists we can work on content.
I am also encouraging someone from our team to contribute upstrean and know that component thoroughly.
-------- Original message --------
From: Rich Bowen <rbowen(a)redhat.com>
Date: 01/23/2014 12:54 PM (GMT-06:00)
To: rdo-list(a)redhat.com
Subject: [Rdo-list] RDO Hangouts: Suggestions/Speakers needed
Last year we had two RDO hangouts, both on networking, and these were
very well received.
We'd like to get this started up again, with hangouts on a variety of
topics. We've had some suggestions in past threads, but nobody
volunteering to do the content.
If you're willing to speak for anywhere from 30 to 45 minutes on any
OpenStack-related topic, please let me know.
Things I'd like to see us do hangouts on include:
* Reporting/Alarming with Ceilometer
* Deploying apps with heat
* Using TryStack
* More stuff about networking, as this continues to be a common pain point
* Icehouse: What's coming
* More advanced deployments with packstack
* ...
I'd also be interested in doing one-on-one hangouts/chats on shorter
topics (10-15 minutes) if that's more your speed than a broadcast type
event.
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
10 years, 9 months
[Rdo-list] Attempt to reproduce Getting Started with Multi-Node OpenStack RDO Havana + Gluster Backend + Neutron VLAN by Andrew Lau on F19
by Boris Derzhavets
Original document
http://www.andrewklau.com/getting-started-with-multi-node-openstack-rdo-h...
contains the sample of answer file. In my situation p37p1 is eth0
p4p1 is eth1 and I've tried to make a substitution in answer-file .
packstack fails with error :
Welcome to Installer setup utility
Packstack changed given value to required value /root/.ssh/id_rsa.pub
Packstack changed given value 192.168.1.137:/CINDER-VOLUMES to required value '192.168.1.137:/CINDER-VOLUMES'
Installing:
Clean Up... [ DONE ]
Setting up ssh keys... [ DONE ]
Discovering hosts' details... [ DONE ]
Adding pre install manifest entries... [ DONE ]
Installing time synchronization via NTP... [ DONE ]
Adding MySQL manifest entries... [ DONE ]
Adding QPID manifest entries... [ DONE ]
Adding Keystone manifest entries... [ DONE ]
Adding Glance Keystone manifest entries... [ DONE ]
Adding Glance manifest entries... [ DONE ]
Installing dependencies for Cinder... [ DONE ]
Adding Cinder Keystone manifest entries... [ DONE ]
Adding Cinder manifest entries... [ DONE ]
Adding Nova API manifest entries... [ DONE ]
Adding Nova Keystone manifest entries... [ DONE ]
Adding Nova Cert manifest entries... [ DONE ]
Adding Nova Conductor manifest entries... [ DONE ]
Adding Nova Compute manifest entries... [ DONE ]
Adding Nova Scheduler manifest entries... [ DONE ]
Adding Nova VNC Proxy manifest entries... [ DONE ]
Adding Nova Common manifest entries... [ DONE ]
Adding Openstack Network-related Nova manifest entries...[ DONE ]
Adding Neutron API manifest entries... [ DONE ]
Adding Neutron Keystone manifest entries... [ DONE ]
Adding Neutron L3 manifest entries... [ DONE ]
Adding Neutron L2 Agent manifest entries... [ DONE ]
Adding Neutron DHCP Agent manifest entries... [ DONE ]
Adding Neutron LBaaS Agent manifest entries... [ DONE ]
Adding Neutron Metadata Agent manifest entries... [ DONE ]
Adding OpenStack Client manifest entries... [ DONE ]
Adding Horizon manifest entries... [ DONE ]
Adding Heat manifest entries... [ DONE ]
Adding Heat Keystone manifest entries... [ DONE ]
Adding Ceilometer manifest entries... [ DONE ]
Adding Ceilometer Keystone manifest entries... [ DONE ]
Adding post install manifest entries... [ DONE ]
Preparing servers... [ DONE ]
Installing Dependencies... [ DONE ]
Copying Puppet modules and manifests... [ DONE ]
Applying Puppet manifests...
Applying 192.168.1.127_prescript.pp
Applying 192.168.1.137_prescript.pp
192.168.1.127_prescript.pp : [ DONE ]
192.168.1.137_prescript.pp : [ DONE ]
Applying 192.168.1.127_ntpd.pp
Applying 192.168.1.137_ntpd.pp
192.168.1.137_ntpd.pp : [ DONE ]
192.168.1.127_ntpd.pp : [ DONE ]
Applying 192.168.1.137_mysql.pp
Applying 192.168.1.137_qpid.pp
192.168.1.137_mysql.pp : [ DONE ]
192.168.1.137_qpid.pp : [ DONE ]
Applying 192.168.1.137_keystone.pp
Applying 192.168.1.137_glance.pp
Applying 192.168.1.137_cinder.pp
192.168.1.137_keystone.pp : [ DONE ]
192.168.1.137_glance.pp : [ DONE ]
192.168.1.137_cinder.pp : [ DONE ]
Applying 192.168.1.137_api_nova.pp
192.168.1.137_api_nova.pp : [ DONE ]
Applying 192.168.1.137_nova.pp
Applying 192.168.1.127_nova.pp
192.168.1.137_nova.pp : [ DONE ]
192.168.1.127_nova.pp : [ DONE ]
Applying 192.168.1.127_neutron.pp
Applying 192.168.1.137_neutron.pp
[ ERROR ]
ERROR : Error appeared during Puppet run: 192.168.1.127_neutron.pp
Error: Validate method failed for class sleep: implicit argument passing of super from method defined by define_method() is not supported. Specify all arguments explicitly.
Disabling Fedora native Ethernet names and switch to eth0 & eth1 on F19 gives same error.
This make an impression that only `packstack --allinone` could work on F19 . I just cannot configure Neutron on
Compute Node with native fedora's ethernet names. It works fine on CentOS 6.4
I would guess that same question would come up for oVirt 3.3.2 Neutron provider on F19 boxes.
How create a server , how create Neutron plugin for oVirt ?
My question is :-
How would look Andrew's https://gist.github.com/andrewklau/7622535/raw/7dac55bbecc200cfb4bf040b61...
for Fedora 19 ?
10 years, 9 months
[Rdo-list] CentOS Cloud Sig efforts
by Mike Burns
There is a meeting scheduled with the CentOS community on Thursday this
week to work out some of the details of the new Cloud SIG. Anyone
interested is welcome to attend (meeting details are below). Rich and I
will be representing the RDO community, and we wanted to reach out to
make sure we cover everything that we want to get out of the new SIG.
Current things we know we want:
* place to deliver common packages like kernel, kvm, etc
* variant that includes RDO packages
* ability to build and deliver CentOS based LiveCD images that contain
RDO code
* ability to build and deliver CentOS based guest images
* ability to build and deliver RDO packages
* Ability to produce custom install media with RDO branding
Please let us know if there are any other things that I'm missing or
that you think should be included.
Thanks
Mike
--
Meeting details:
I'd like to invite everyone wanting to contribute to the Cloud SIG and
representing a project outside centos.org to come along for a chat on
google hangout at the CentOS OfficeHours 23rd Jan 2014 @ 16:00 UTC.
Because we only have a few slots for people to talk, I've shortlisted
these folks:
OpenStack: Mike Burns, Dave Neary, Rich Bowen
Eucalyptus: Greg DK
OpenNebula: Jaime Melis
CloudStack: Sebastien Goasguen
oVirt: Doron Fediuck
If you want to be on this list, please get in touch. If you are on this
list but cant make it at that date/time, please nominate someone else in
your place and let me know their email address so I can notify them of
the url to join.
This will be a video/audio session and will be publicly broadcast over
youtube/hangouts on air; the recording of the session will be available
immediately after. Bonus cookies for everyone who turns up in their
project tshirts!
You can see what time that is on your local timezone at this url :
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140123T16&am=30
About the session:
- Plan on an hour
- Every project should do a few minutes worth of a pitch about what they
would like to see as a good first goal and a good longer term goal.
- We can then discuss delivery mechanis, and how the forward maintenance
of the projects payload is going to work ( essentially, workout how the
rpms will map to os/ and updates/ )
- Consider the workflow from git.centos.org ( KB to do a 5 min demo )
10 years, 9 months
[Rdo-list] RDO Bug triage efforts
by Mike Burns
As part of the effort to triage bugs filed against RDO components, we're
trying come up with sane default assignees for each component.
Currently, most bugs get assigned to "RHOS Maint" by default which means
that the right people aren't getting notified automatically.
We do have other efforts going to try to get a consistent process for
RDO bugs in place, but that will come a little later.
What we would like to do is have people update a wiki page[1] with a
default contact for each component and anyone you want to get cc'ed on
bug updates. Once we have contacts for each component, I'll coordinate
with the bugzilla team to apply the changes to bugzilla.
Thanks in advance for helping to fill out this page.
Mike
[1] http://openstack.redhat.com/Bugzilla_ownership
10 years, 9 months
