Re: [openstack-dev] Missing button to send Ctrl+Alt+Del for SPICE Console

Sorry to resurrect this almost a year later! I've recently run into this issue, and it does make logging into Windows instances, via the console, quite challenging. On Fri, Jun 6, 2014 at 3:46 PM, Ben Nemec openst...@nemebean.com wrote: This sounds like a reasonable thing to open a bug against

Re: [openstack-dev] [os-ansible-deployment] Core nomination for Matt Kassawara (sam-i-am)

Matt does add value, and I definitely don't want to imply that what he does isn't great work or that it isn't helpful to the project, however its hard to +1 a Core reviewer who has 1 review in the liberty timeframe. Since one of the primary purposes of core reviewers is to actively review code it

Re: [openstack-dev] [openstack-ansible] Proposing Steve Lewis (stevelle) for core reviewer

+1 from me. On 30 September 2015 at 09:51, Jesse Pretorius wrote: > Hi everyone, > > I'd like to propose that Steve Lewis (stevelle) be added as a core > reviewer. > > He has made an effort to consistently keep up with doing reviews in the > last cycle and always

[openstack-dev] [OpenStack-Ansible] Splitting out generic testing components

TL;DR We're doing a PoC to split out common testing plays/vars into a generic repository, for the purposes of making in-role testing more uniform and generic. Looking for feedback, comments, informal reviews, ideas etc! https://github.com/andymcc/openstack-ansible-testing-core (Includes a simple

Re: [openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security

+1 Ship it. Andy On 6 May 2016 at 07:42, Jesse Pretorius wrote: > On 3 May 2016 at 23:59, Jim Rollenhagen wrote: > >> >> Sounds like a major win for the team! > > > Haha! Quite! > > +1 for me on the proposal. I've spoken to Major and

Re: [openstack-dev] [openstack-ansible] Propose Marc Gariepy as core reviewer

Definite +1 from me. Thanks for all the work on CentOS Marc, looking forward to improving upon that with your help! On 3 February 2017 at 13:33, Jesse Pretorius < jesse.pretor...@rackspace.co.uk> wrote: > Hi everyone, > > > > I’d like to propose Marc Gariepy [1] as a core reviewer for >

[openstack-dev] [openstack-ansible] [ptl] PTL Candidacy for Pike

Hi All, I'm once again running for the PTL position for OpenStack-Ansible during the Pike cycle. Here is my candidacy statement: https://review.openstack.org/#/c/424348/ Thanks for all your support during the Ocata cycle, and looking forward to Pike! Andy

Re: [openstack-dev] [openstack-ansible] Proposing Amy Marrich for core

+1 from me too. Thanks for your contributions so far Amy, glad to have you as part of the community. Andy __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [release][ansible] release job failure for openstack-ansible docs

On 23 February 2017 at 16:54, Doug Hellmann wrote: > This looks like an issue with the node (filesystem corruption?) but just > in case it's reproducible I'm forwarding the link to the logs. > > Doug > > --- Begin forwarded message from jenkins --- > From: jenkins

Re: [openstack-dev] [openstack-ansible] So long, farewell, auf wiedersehen

Thanks again Travis - it's been great to have your input and help on so many of the decisions made within OSA over the last year and a bit. You'll definitely be missed, and I wish you all the best for the future! Andy __

Re: [openstack-dev] [deployment][TripleO][kolla][ansible][fuel] Next steps for cross project collaboration

On 2 March 2017 at 10:18, Steven Hardy wrote: > On Thu, Mar 02, 2017 at 05:06:34AM +, Brandon B. Jozsa wrote: > >+1 for the monthly meetings and a long standing, cross-team, > collaborative > >etherpad. > > Yes the etherpad is a good idea, thanks! > > I guess we'll

Re: [openstack-dev] [Openstack-operators] [openstack-operators][openstack-ansible]deploying mutli-node openstack on baremetal nodes

Hi Akshay, If I understand correctly, you're looking to deploy the services on metal hosts (rather than in containers) - in that case you would need to adjust the env.d/*.yml (service files) to set the property "is_metal: True". The second query regarding multiple VLans - if you are using

Re: [openstack-dev] [Openstack-operators] [all] [goals] proposing a new goal: "Control Plane API endpoints deployment via WSGI"

> > > I have been looking for a Community Goal [1] that would directly help > Operators and I found the "run API via WSGI" useful. > So I've decided to propose this one as a goal for Pike but I'll stay > open to postpone it to Queen if our community thinks we already have > too much goals for

Re: [openstack-dev] [os-ansible-deployment] Periodic job in infra to test upgrades?

Hi Sean, > OK - is this a job in Zuul ? Where can I find more information? > They are Zuul jobs, and are currently non-voting (but should be passing - we're waiting to ensure the tests are reliably passing before moving to voting). The test is essentially: Deploy infra for testing Deploy

Re: [openstack-dev] [os-ansible-deployment] Periodic job in infra to test upgrades?

> > > OK - is there any way that I can assist? > > What about the challenges I discussed in my initial mail related to > long AIO build times etc..? > > I think there are some options, but the idea we're going with at the moment is to look into setting this up as a periodical - we're at about 1hr

Re: [openstack-dev] [os-ansible-deployment] Periodic job in infra to test upgrades?

> > > Ah OK I see now. > > I guess what I'm driving at, is how do we get automated coverage for the > full end-to-end upgrade, so that issues[1] that I uncovered during manual > testing start getting uncovered by automation? > > [1]: https://review.openstack.org/#/c/400847/ Completely agree, the

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

Sorry to resurrect a few weeks old thread, but I had a few questions. > Yes, we should stop with the magic ports. Part of the reason of > switching over to apache was to alleviate all of that. > > -Sean > Is this for devstack specifically? I can see the motivation for Devstack, since it

Re: [openstack-dev] [os-ansible-deployment] Periodic job in infra to test upgrades?

Hi Sean, I assume you're talking about OpenStack-Ansible (was OS-A-D before moving to the OpenStack namespace), if not, feel free to ignore my response! This is actually something we're working on - we have in role testing for some key OpenStack services (Nova, Neutron, Swift, Keystone, Cinder,

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

Hi Tony, > Please look over both lists by 2017-04-17 00:00 UTC and let me know if: > - A project is in list 1 and *really* *really* wants to opt *OUT* of > EOLing and > why. Note doing this will amost certainly reduce the testing coverage > you > have in the gate. > - A project is in list 2

Re: [openstack-dev] [nova][docs] Broken nova instructions

On 9 March 2017 at 12:05, Alexandra Settle wrote: > > > On 3/9/17, 10:36 AM, "Sylvain Bauza" wrote: > > > > Le 09/03/2017 11:25, Alexandra Settle a écrit : > > Hi everyone, > > > > > > > > The installation guide for docs.o.o is

Re: [openstack-dev] [openstack-ansible] [nova] Compute node failing to come up in hypervisor list after first reboot

Hey Lawrence, The nc -z is checking that you can connect to the port, but the error itself looks to be related to the handshake when using SSL certificates in rabbitmq. "getrandom() initialization failed. (_ssl.c:590)" being the important bit there. You'll probably find more if you start

Re: [openstack-dev] Ansible OpenStack dnsmasq errors in syslog

Hi Lawrence, Thanks for raising this. The 10.255.255.x range is used by lxcbr0 on the host, to assign the eth0 address to the containers. In essence this won't cause any issues - since we use the eth1 address (which is statically configured) and we add the host entries to /etc/hosts. That said,

Re: [openstack-dev] [deployment][TripleO][kolla][ansible][fuel] Next steps for cross project collaboration

On 28 February 2017 at 08:25, Flavio Percoco wrote: > On 28/02/17 08:01 +, Jesse Pretorius wrote: > >> On 2/28/17, 12:52 AM, "Michał Jastrzębski" wrote: >> >>I think instead of adding yet-another-irc-channel how about create >>weekly meetings? We

[openstack-dev] [OpenStack-Ansible] Not running for Queens PTL

Following on from last week's meeting - I've had 2 cycles as PTL for OSA, which has been a really great experience - we've achieved a lot and built on the strong base we had, which I'm really proud of. I strongly believe that inviting a fresh perspective and new ideas as PTL is a winning strategy

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

Hi Andreas, OK, added. I'm waiting for packstack confirmation. > > The current list is now: > > > openstack/sahara-extra stable/icehousePlease retire > openstack/sahara-extra stable/mitaka Please retire > openstack/packstack stable/kiloWaiting for

[openstack-dev] [OpenStack-Ansible] Proposing Markos Chandras for osa-core

Following on from last week's meeting I'd like to propose Markos (hwoarang) for OSA core. Markos has done a lot of good reviews and commits over an extended period of time, and has shown interest in the project as a whole. (Not to mention the addition of SUSE support) We already have quite a few

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

> > > > The branches have now been retired, thanks to Joshua Hesketh! > Thanks Josh, Andreas, Tony, and the rest of the Infra crew for sorting this out. Andy __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [kolla][TripleO] New areas for collaboration between Kolla and TripleO

Hi all, > > > Some areas of collaboration: > > * Kubernetes resources: Work on the same set of resources. In this case, > resources means the existing templates in kolla-kubernetes. Find ways to > share > the same resources rather than having 2 different sets of resources. > > * Configuration

Re: [openstack-dev] (no subject)

Hi Lawrence, On 4 July 2017 at 12:29, Lawrence J. Albinson wrote: > Dear Colleagues, > > Before I go problem hunting, has anyone seen openstack-ansible builds > failing at release 15.1.5 at the following point: > > TASK [lxc_container_create : Create localhost config] >

Re: [openstack-dev] [Openstack] OpenStack-Ansible HA solution

Hi Maxwell, > > I have some questions about OSA project. > > > > 1. OSA can install haproxy, but I can not found any other HA > solution in openstack-ansible-haproxy_server, like keepalived or > pacemarker. So how to making HAproxy high-available? > Take a look at:

Re: [openstack-dev] 答复: [Openstack] OpenStack-Ansible HA solution

Hi Maxwell, I found that OSA use keepalived to resolve controller HA, but whether the > keepalived support compute HA? What shoud I do or which file I need to > config if I want to resolve compute HA? > > > > And there are some solutions for compute HA in this web: >

Re: [openstack-dev] [openstack-ansible][designate] Recommended way to inject the rndc.key into the designate container when using Bind9

Hi Lawrence, Thanks for providing the feedback! I am using OpenStack Designate with Bind9 as the slave and have managed to > set it up with openstack-ansible in all respect bar one, I am unable to > automatically inject the rndc.key file into the Designate container. > Is there a recognised way

Re: [openstack-dev] [openstack-ansible] group/host specific config file overrides: how-to?

Hey Markus, > I'm wondering which possibilities I have to do group/host specific > config file overrides. After reading [1], I'm still a little clueless. > To be specific, I have this setup (expressed as Ansible inventory file): > > [z_compute_nodes] > compute1 > # more nodes >

Re: [openstack-dev] [openstack-ansible] Implement rotations for meetings handling

> > > Now that we are all part-time, I'd like to toy with a new idea, > proposed in the past by Jesse, to rotate the duties with people who > are involved in OSA, or want to get involved more (it's not restricted > to core developers!). > > One of the first duties to be handled this way could be

[openstack-dev] [openstack-ansible] Stepping down from OpenStack-Ansible core

Now that Rocky is all but ready it seems like a good time! Since changing roles I've not been able to keep up enough focus on reviews and other obligations - so I think it's time to step aside as a core reviewer. I want to say thanks to everybody in the community, I'm really proud to see the work