[Openstack-operators] automatically evacuate an instance when a compute node dies
Hi all, is there a working solution in nova to automatically restart an instance when a compute node dies in a healthy node? I've heard about pacemaker, any good howto to help with this? Regards ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Packaging sample config versions
On 2014-12-08 11:01 PM, Kris G. Lindgren wrote: I don’t think its too much to ask for each project to include a script that will build a venv that includes tox and the other relevant deps to build the sample configuration. This is already the case. Back then, I did the work of documenting how you could generate the sample config files for each projects (I cared about): http://blog.mgagne.ca/generating-sample-config-files-in-openstack/ You can see that the process isn't streamlined. Each project has its own particularities. Some projects don't use the (un)official standard tox -egenconfig command, I patched some projects to make it less a pain. And my thoughts about sample config files: http://blog.mgagne.ca/where-are-the-sample-config-files/ I wrote it after Cinder proposed removing its sample config file. They abandoned the patch at that time but now sample config file is gone. It's not an easy problem because core libraries used by OpenStack projects also use oslo.config and configs required by those libraries are part of the main configurations required for a project to even work. ([database]/connection for instance) You just can't ignore those configs when generating the sample config file. (sorry for self-promotion, I didn't want to rewrite my thoughts on this list) -- Mathieu ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Packaging sample config versions
So more to my point on the latest version of RHEL and doing: yum install
tox -egenconfig
ceilometer-2014.2.1]# tox -egenconfig
ERROR: tox version is 1.4.2, required is at least 1.6
nova-2014.2.1]# tox -egenconfig
ERROR: tox version is 1.4.2, required is at least 1.6
glance-2014.2.1]# tox -egenconfig
ERROR: tox version is 1.4.2, required is at least 1.6
[root@localhost ~]# pip install --update tox
(Updated tox to 1.8.1 , upgraded virtualenv to 1.10.1 and upgraded py to
1.4.14)
glance-2014.2.1]# tox -egenconfig
genconfig create: /root/rpmbuild/BUILD/glance-2014.2.1/.tox/genconfig
genconfig installdeps:
-r/root/rpmbuild/BUILD/glance-2014.2.1/requirements.txt,
-r/root/rpmbuild/BUILD/glance-2014.2.1/test-requirements.txt
ERROR: invocation failed (exit code 1), logfile:
/root/rpmbuild/BUILD/glance-2014.2.1/.tox/genconfig/log/genconfig-1.log
ERROR: actionid=genconfig
SNIP
Running setup.py install for MySQL-python
SNIP
/usr/include/mysql/my_config_x86_64.h:654:2: error: #error
my_config.h MUST be included first!
#error my_config.h MUST be included first!
^
error: command 'gcc' failed with exit status 1
snip
__ summary
__
ERROR: genconfig: could not install deps
[-r/root/rpmbuild/BUILD/glance-2014.2.1/requirements.txt,
-r/root/rpmbuild/BUILD/glance-2014.2.1/test-requirements.txt]; v =
InvocationError('/root/rpmbuild/BUILD/glance-2014.2.1/.tox/genconfig/bin/pi
p install --allow-all-external --allow-insecure netaddr -U
-r/root/rpmbuild/BUILD/glance-2014.2.1/requirements.txt
-r/root/rpmbuild/BUILD/glance-2014.2.1/test-requirements.txt (see
/root/rpmbuild/BUILD/glance-2014.2.1/.tox/genconfig/log/genconfig-1.log)',
1)
So a few things to point out in order to even get tox -egenconfig I had to
update the system packages versions using pip. Since we have other python
packages using virtualenv I have no idea if the updated venvironment
package is going to break those systems or not. So the included
script/command is already a barrier to getting a sample config. 2) tox
fails to even build all the deps - it happens to be exactly failing at
mysql in both nova/cinder/glance/keystone 3) It's installing it own
versions of python libraries that solve the dependencies that are then
going to be used to generate the configuration. If the configuration is
so dynamic that getting a different version of oslo.config could generate
a sample configuration that wont work on my system then how am I suppose
to deal with:
Tox installed version:
oslo.config-1.5.0
System installed version:
python-oslo-config-1.3.0
Also python-libvrit failed to build because I don¹t have libvrit installed
on this system. So am I to assume that there are no libvrit options
(which we both know is false)?
Now I can get a example config - that wont work with my system - per what
everyone else has been saying. Also, at what point would the average user
just say F it? - because at the point I feel like if I was an average
user - I would be there right now.
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy, LLC.
On 12/9/14, 8:14 AM, Mathieu Gagné mga...@iweb.com wrote:
On 2014-12-08 11:01 PM, Kris G. Lindgren wrote:
I don¹t think its too much to ask for each project to include a script
that will build a venv that includes tox and the other relevant deps to
build the sample configuration.
This is already the case. Back then, I did the work of documenting how
you could generate the sample config files for each projects (I cared
about):
http://blog.mgagne.ca/generating-sample-config-files-in-openstack/
You can see that the process isn't streamlined. Each project has its own
particularities. Some projects don't use the (un)official standard tox
-egenconfig command, I patched some projects to make it less a pain.
And my thoughts about sample config files:
http://blog.mgagne.ca/where-are-the-sample-config-files/
I wrote it after Cinder proposed removing its sample config file. They
abandoned the patch at that time but now sample config file is gone.
It's not an easy problem because core libraries used by OpenStack
projects also use oslo.config and configs required by those libraries
are part of the main configurations required for a project to even work.
([database]/connection for instance) You just can't ignore those configs
when generating the sample config file.
(sorry for self-promotion, I didn't want to rewrite my thoughts on this
list)
--
Mathieu
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Packaging sample config versions
Well I think we can all agree this is an irritation. But how are others
actually dealing with this problem? (Maybe it’s less complicated in
Ubuntu.)
The sense I get is that most people using Anvil, or other custom-ish
packaging tools, are also running config management which handles
generating the config files, anyway. So you don’t so much care about the
contents of the config file shipped with the package.
Is that accurate for most people? Or are folks doing some other magic to
get a good config file in the packages?
Mike
On 12/9/14, 5:02 PM, Kris G. Lindgren klindg...@godaddy.com wrote:
So more to my point on the latest version of RHEL and doing: yum install
tox -egenconfig
ceilometer-2014.2.1]# tox -egenconfig
ERROR: tox version is 1.4.2, required is at least 1.6
nova-2014.2.1]# tox -egenconfig
ERROR: tox version is 1.4.2, required is at least 1.6
glance-2014.2.1]# tox -egenconfig
ERROR: tox version is 1.4.2, required is at least 1.6
[root@localhost ~]# pip install --update tox
(Updated tox to 1.8.1 , upgraded virtualenv to 1.10.1 and upgraded py to
1.4.14)
glance-2014.2.1]# tox -egenconfig
genconfig create: /root/rpmbuild/BUILD/glance-2014.2.1/.tox/genconfig
genconfig installdeps:
-r/root/rpmbuild/BUILD/glance-2014.2.1/requirements.txt,
-r/root/rpmbuild/BUILD/glance-2014.2.1/test-requirements.txt
ERROR: invocation failed (exit code 1), logfile:
/root/rpmbuild/BUILD/glance-2014.2.1/.tox/genconfig/log/genconfig-1.log
ERROR: actionid=genconfig
SNIP
Running setup.py install for MySQL-python
SNIP
/usr/include/mysql/my_config_x86_64.h:654:2: error: #error
my_config.h MUST be included first!
#error my_config.h MUST be included first!
^
error: command 'gcc' failed with exit status 1
snip
__ summary
__
ERROR: genconfig: could not install deps
[-r/root/rpmbuild/BUILD/glance-2014.2.1/requirements.txt,
-r/root/rpmbuild/BUILD/glance-2014.2.1/test-requirements.txt]; v =
InvocationError('/root/rpmbuild/BUILD/glance-2014.2.1/.tox/genconfig/bin/p
i
p install --allow-all-external --allow-insecure netaddr -U
-r/root/rpmbuild/BUILD/glance-2014.2.1/requirements.txt
-r/root/rpmbuild/BUILD/glance-2014.2.1/test-requirements.txt (see
/root/rpmbuild/BUILD/glance-2014.2.1/.tox/genconfig/log/genconfig-1.log)',
1)
So a few things to point out in order to even get tox -egenconfig I had to
update the system packages versions using pip. Since we have other python
packages using virtualenv I have no idea if the updated venvironment
package is going to break those systems or not. So the included
script/command is already a barrier to getting a sample config. 2) tox
fails to even build all the deps - it happens to be exactly failing at
mysql in both nova/cinder/glance/keystone 3) It's installing it own
versions of python libraries that solve the dependencies that are then
going to be used to generate the configuration. If the configuration is
so dynamic that getting a different version of oslo.config could generate
a sample configuration that wont work on my system then how am I suppose
to deal with:
Tox installed version:
oslo.config-1.5.0
System installed version:
python-oslo-config-1.3.0
Also python-libvrit failed to build because I don¹t have libvrit installed
on this system. So am I to assume that there are no libvrit options
(which we both know is false)?
Now I can get a example config - that wont work with my system - per what
everyone else has been saying. Also, at what point would the average user
just say F it? - because at the point I feel like if I was an average
user - I would be there right now.
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy, LLC.
On 12/9/14, 8:14 AM, Mathieu Gagné mga...@iweb.com wrote:
On 2014-12-08 11:01 PM, Kris G. Lindgren wrote:
I don¹t think its too much to ask for each project to include a
script
that will build a venv that includes tox and the other relevant deps to
build the sample configuration.
This is already the case. Back then, I did the work of documenting how
you could generate the sample config files for each projects (I cared
about):
http://blog.mgagne.ca/generating-sample-config-files-in-openstack/
You can see that the process isn't streamlined. Each project has its own
particularities. Some projects don't use the (un)official standard tox
-egenconfig command, I patched some projects to make it less a pain.
And my thoughts about sample config files:
http://blog.mgagne.ca/where-are-the-sample-config-files/
I wrote it after Cinder proposed removing its sample config file. They
abandoned the patch at that time but now sample config file is gone.
It's not an easy problem because core libraries used by OpenStack
projects also use oslo.config and configs required by those libraries
are part of the main configurations required for a
Re: [Openstack-operators] Weekly Irc meeting?
56 Openstack Operators Team Meeting https://wiki.openstack.org/wiki/Meetings#Openstack_Operators_Team_Meeting On Dec 9, 2014, at 9:54 AM, Abel Lopez alopg...@gmail.com wrote: According to the iCal feed, 1800 UTC on 12/17, we have #openstack-meeting, and #openstack-meeting-4 available. We should put that on the calendar. On Dec 9, 2014, at 5:34 AM, Michael Chapman wop...@gmail.com mailto:wop...@gmail.com wrote: Hi folks, There wasn't much response to the previous meeting time, so I'd like to propose another time for regular irc meetings to try to make progress on the 'Operations Project' goals: 1800 UTC Wednesday 17th December in #openstack-operators. Here's an etherpad for an agenda: https://etherpad.openstack.org/p/openstack-operators-meeting-171214-agenda https://etherpad.openstack.org/p/openstack-operators-meeting-171214-agenda -Michael ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org mailto:OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Weekly Irc meeting?
I’ve started some work on the agenda in the ether pad. Feel free to promote or demote topics. Two areas that I know are under active discussion are the sample config files or lack thereof and ansible mysql upgrades and I’d also like to talk about the mailing list some. Feel free to add or modify. Note: The meeting WILL Be in #openstack-meeting-4, not in #openstack-operators. Hope to see everyone there. From: Michael Chapman wop...@gmail.commailto:wop...@gmail.com Date: Tuesday, December 9, 2014 at 6:34 AM To: openstack-operators@lists.openstack.orgmailto:openstack-operators@lists.openstack.org openstack-operators@lists.openstack.orgmailto:openstack-operators@lists.openstack.org Subject: [Openstack-operators] Weekly Irc meeting? Hi folks, There wasn't much response to the previous meeting time, so I'd like to propose another time for regular irc meetings to try to make progress on the 'Operations Project' goals: 1800 UTC Wednesday 17th December in #openstack-operators. Here's an etherpad for an agenda: https://etherpad.openstack.org/p/openstack-operators-meeting-171214-agenda -Michael This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] GPG signatures failed for OpenStack Icehouse EPEL repo
- Original Message - From: Kris G. Lindgren klindg...@godaddy.com To: Edgar Magana edgar.mag...@workday.com, openst...@lists.openstack.org, openstack-operators@lists.openstack.org I don’t use the RDO packages – however my guess is you need to verify using the rdo-icehouse gpg key: https://github.com/redhat-openstack/rdo-release/blob/icehouse/RPM-GPG-KEY-RDO-Icehouse But I am not sure where they keep that key publicly downloadable outside of their github repo. It's in the release RPM you install to add the repository: https://repos.fedorapeople.org/repos/openstack/openstack-icehouse/rdo-release-icehouse-4.noarch.rpm From: Edgar Magana edgar.mag...@workday.commailto:edgar.mag...@workday.com Date: Monday, December 8, 2014 at 4:41 PM To: openst...@lists.openstack.orgmailto:openst...@lists.openstack.org openst...@lists.openstack.orgmailto:openst...@lists.openstack.org, openstack-operators@lists.openstack.orgmailto:openstack-operators@lists.openstack.org openstack-operators@lists.openstack.orgmailto:openstack-operators@lists.openstack.org Subject: [Openstack-operators] GPG signatures failed for OpenStack Icehouse EPEL repo Hello, I am not sure if this is the right audience for this question but I would like to give it a try and maybe get re-directed to the right one. I tried verifying GPG signatures on RPMs in the OpenStack Icehouse EPEL repo (http://repos.fedorapeople.org/repos/openstack/openstack-icehouse/epel-6 ). All of them failed (see below). This page here says the packages should be verifiable with the EPEL GPG keys: http://docs.openstack.org/icehouse/install-guide/install/yum/content/basics-packages.html The EPEL packages that statement is referring to (the repository for which is installed by the command that follows) are signed using the EPEL key, the RDO packages are signed using the RDO key. -Steve ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [Telco][NFV] Meeting Reminder - Wednesday Dec 9 @ 2200 UTC in #openstack-meeting
Hi all, Just a reminder that the Telco Working Group will be meeting @ 2200 UTC in #openstack-meeting on Wednesday December 9th. Draft agenda is available here: https://etherpad.openstack.org/p/nfv-meeting-agenda Please feel free to add anything you think I missed. Thanks, Steve ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [Telco][NFV] Meeting Reminder - Wednesday Dec 10 @ 2200 UTC in #openstack-meeting
...and of course I meant December *10th* - sorry! -Steve - Original Message - From: Steve Gordon sgor...@redhat.com Hi all, Just a reminder that the Telco Working Group will be meeting @ 2200 UTC in #openstack-meeting on Wednesday December 9th. Draft agenda is available here: https://etherpad.openstack.org/p/nfv-meeting-agenda Please feel free to add anything you think I missed. Thanks, Steve -- Steve Gordon, RHCE Sr. Technical Product Manager, Red Hat Enterprise Linux OpenStack Platform ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
