- openstack-discuss - lists.openstack.org

[ops] Ops Meetup proposal, Berlin, early 2019
by Chris Morgan 04 Dec '18

04 Dec '18

Hello Everyone, Deutsche Telekom has kindly offered to host an OpenStack Operators Meetup early next year see https://etherpad.openstack.org/p/ops-meetup-venue-discuss-1st-2019-berlin This is the only current offer so far for the first Ops Meetup of 2019 so is very likely to be approved. If you have feedback on this please join us at our weekly IRC meeting or forward your feedback to an Ops Meetups Team member (see https://wiki.openstack.org/wiki/Ops_Meetups_Team for details of the current team). This proposal meets the consensus goal of Europe as the region for the 1st meetup, making it likely that the following one later in 2019 would be in North America. Chris -- Chris Morgan <mihalis68(a)gmail.com>

1 0

[ops] last week's Ops Meetups team minutes
by Chris Morgan 04 Dec '18

04 Dec '18

Meeting ended Tue Nov 27 15:56:56 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 10:57 AM Minutes: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_tea… 10:57 AM Minutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_tea… 10:57 AM Log: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_tea… Next meeting in just under an hour from now on #openstack-operators Chris -- Chris Morgan <mihalis68(a)gmail.com>

1 0

[neutron] [octavia] Manual deployment step for octavia on packstack
by Vikrant Aggarwal 04 Dec '18

04 Dec '18

Hello Team, Do we have the steps documented somewhere to install octavia manually like we have for zun [1]? I have done the openstack deployment using packstack and now I want to install the octavia manually on it. I have done the following steps: # groupadd --system octavia # useradd --home-dir "/var/lib/octavia" --create-home --system --shell /bin/false -g octavia octavia # cd /var/lib/octavia/ # git clone https://github.com/openstack/octavia.git # chown -R octavia:octavia * # pip install -r requirements.txt # python setup.py install # openstack user create --domain default --password-prompt octavia # openstack role add --project service --user octavia admin # openstack service create --name octavia --description "Octavia Service" "Octavia Load Balancing Servic" # openstack endpoint create --region RegionOne "Octavia Load Balancing Servic" public http://10.121.19.50:9876/v1 # openstack endpoint create --region RegionOne "Octavia Load Balancing Servic" admin http://10.121.19.50:9876/v1 # openstack endpoint create --region RegionOne "Octavia Load Balancing Servic" internal http://10.121.19.50:9876/v1 Made the following changes in the configuration file. [root@packstack1 octavia(keystone_admin)]# diff etc/octavia.conf /etc/octavia/octavia.conf 20,21c20,21 < # bind_host = 127.0.0.1 < # bind_port = 9876 --- > bind_host = 10.121.19.50 > bind_port = 9876 38c38 < # api_v2_enabled = True --- > # api_v2_enabled = False 64c64 < # connection = mysql+pymysql:// --- > connection = mysql+pymysql://octavia:octavia@10.121.19.50/octavia 109c109 < # www_authenticate_uri = https://localhost:5000/v3 --- > www_authenticate_uri = https://10.121.19.50:5000/v3 111,114c111,114 < # auth_url = https://localhost:5000/v3 < # username = octavia < # password = password < # project_name = service --- > auth_url = https://10.121.19.50:35357/v3 > username = octavia > password = octavia > project_name = service 117,118c117,118 < # project_domain_name = Default < # user_domain_name = Default --- > project_domain_name = default > user_domain_name = default Generated the certificates using the script and copy the following certificates in octavia: [root@packstack1 octavia(keystone_admin)]# cd /etc/octavia/ [root@packstack1 octavia(keystone_admin)]# ls -lhrt total 28K -rw-r--r--. 1 octavia octavia 14K Dec 4 05:50 octavia.conf -rw-r--r--. 1 octavia octavia 1.7K Dec 4 05:55 client.key -rw-r--r--. 1 octavia octavia 989 Dec 4 05:55 client.csr -rw-r--r--. 1 octavia octavia 1.7K Dec 4 05:55 client.pem Can anyone please guide me about the further configuration? [1] https://docs.openstack.org/zun/latest/install/controller-install.html Thanks & Regards, Vikrant Aggarwal

1 0

[dev] [tc][all] TC office hours is started now on #openstack-tc
by Ghanshyam Mann 04 Dec '18

04 Dec '18

Hello everyone, TC office hour is started on #openstack-tc channel. Feel free to reach to us for anything you want discuss/input/feedback/help from TC. - gmann & TC

1 0

[openlab] Weekly Meeting
by Melvin Hillsman 03 Dec '18

03 Dec '18

Hi everyone, Please see the following links for full log of today’s meeting and a more concise summary: Full Log: https://meetings.openlabtesting.org/devops/2018/devops.2018-12-04-02.00.log… Summary (Minutes): https://meetings.openlabtesting.org/devops/2018/devops.2018-12-04-02.00.html Help Wanted: Setup os_loganalyze – https://github.com/theopenlab/openlab/issues/137 There is always an opportunity to grab items off the project board – https://github.com/orgs/theopenlab/projects/1 If you have any questions regarding the meeting please send email response to this email for follow-up. -- Kind regards, Melvin Hillsman mrhillsman(a)gmail.com mobile: (832) 264-2646

1 0

[openstack-dev] [Neutron] Bugs deputy report week of November 26th
by Miguel Lavalle 03 Dec '18

03 Dec '18

Hi Neutron team, I was the bugs deputy the week of November 26th. It was a relatively quite week. These are the bugs reported during the period: *Medium priority* - https://bugs.launchpad.net/neutron/+bug/1805824, The dhcp port's address may be messed when the port's network has multiple subnets. Fix proposed here: https://review.openstack.org/#/c/620900/. It undoes a previous fix, https://bugs.launchpad.net/neutron/+bug/1581918, so another alternative has to be found - https://bugs.launchpad.net/neutron/+bug/1805808, Openvswitch firewall driver don't reinitialize after ovs-vswitchd restart. Fix proposed here: https://review.openstack.org/620886 - https://bugs.launchpad.net/neutron/+bug/1805456, [DVR] Neutron doesn't configure multiple external subnets for one network properly. Owner assigned *Low priority* - https://bugs.launchpad.net/neutron/+bug/1805844*, *When debugging fullstack tests, "cmd" module is incorrectly imported*. *Fix already in progress: https://review.openstack.org/620916 - https://bugs.launchpad.net/neutron/+bug/1805126, confusing wording in config-dns-int.rst. Fixed proposed: https://review.openstack.org/620017 *Incomplete* - https://bugs.launchpad.net/neutron/+bug/1805769, maximum RPC response timeout is not reasonable. Requested clarification from submitter - https://bugs.launchpad.net/neutron/+bug/1805356, Convert instance method to staticmethod in linux bridge agent. Requested clarification from submitter *Needs further investigation* - https://bugs.launchpad.net/neutron/+bug/1805132, bulk creation of security group rules fails StaleDataError. Couldn't reproduce

1 0

[openstack-dev] [magnum] kubernetes images for magnum rocky
by Spyros Trigazis 03 Dec '18

03 Dec '18

Hello all, Following the vulnerability [0], with magnum rocky and the kubernetes driver on fedora atomic you can use this tag "v1.11.5-1" [1] for new clusters. To upgrade the apiserver in existing clusters, on the master node(s) you can run: sudo atomic pull --storage ostree docker.io/openstackmagnum/kubernetes-apiserver:v1.11.5-1 sudo atomic containers update --rebase docker.io/openstackmagnum/kubernetes-apiserver:v1.11.5-1 kube-apiserver You can upgrade the other k8s components with similar commands. I'll share instructions for magnum queens tomorrow morning CET time. Cheers, Spyros [0] https://github.com/kubernetes/kubernetes/issues/71411 [1] https://hub.docker.com/r/openstackmagnum/kubernetes-apiserver/tags/ __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 2

[all] We've combined the lists! Now what?
by Jeremy Stanley 03 Dec '18

03 Dec '18

As previously discussed[0], proposed[1] and subsequently announced[2], the openstack, openstack-dev, openstack-sigs and openstack-operators mailing lists are being replaced by this new mailing list to which you've subscribed. As of now it's officially open for posts from subscribers, and the old lists will be configured to no longer accept posts starting on Monday December 3. In the interim, posts to the old lists will also get copied to the new list so it's safe to unsubscribe from them now and not miss any messages. Here follows few brief notes on the nature of this new list: 1. Like mentioned in the original announcement, there is an etherpad[3] where we can brainstorm subject tags we want to use. I think most of our needs are already covered there, but I'll give it a little longer to collect more ideas before I attempt to document them somewhere durable. We've already got these as a start: all, ops, dev, $projectname, $signame-sig, $groupname-wg, release, goals, uc, tc, ptl. Because we're interested in moving to Mailman 3 as our listserv in the not-too-distant future and the upstream Mailman maintainers decided to drop support for server-side topic filters, you'll need to set up client-side mail filtering if you're only interested in seeing messages for a subset of them. 2. As I've subscribed the new list to the old ones, cross-posts between them may result in some message duplication, but at least we won't have to endure it for long. 3. Remember there is no Subject header mangling on this list, so if you want to perform client-side matching it's strongly recommended you use the List-Id header to identify it. You'll likely also notice there is no list footer appended to every message. These changes in behavior from our previous lists are part of an effort to avoid creating unnecessary DMARC/DKIM violations. 4. This list is starting out with 280 early subscribers, but I expect a bunch more before the old lists are finally closed down in 3 weeks' time. [0] https://etherpad.openstack.org/p/infra-ptg-denver-2018 [1] http://lists.openstack.org/pipermail/openstack-dev/2018-August/134046.html [2] http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.ht… [3] https://etherpad.openstack.org/p/common-openstack-ml-topics -- Jeremy Stanley

5 9

[nova][ops] Migrating instances with old extra specs info.
by Roman Dobosz 03 Dec '18

03 Dec '18

Hi, We have an issue regarding live migrate old instances. On our infrastructure based on Newton, we had not well named our aggregation groups and we decided to completely change the naming conventions. We are using extra specs/metadata in flavors/aggregates and AggregateInstanceExtraSpecsFilter to select the set of hosts. After changing one of the key (lets call it 'kind') of extra spec/metadata to the new value, we are able to create new instances, but unable to live-migrate old one. This is because of stored flavor extra specs in instance_extra, which still holds the old value for the 'kind' key, and make the aggregate filter fail to match the hosts. In our opinion, it should be able to live-migrate such instance, since only the flavor metadata has changed, while other fields doesn't (vcpus, memory, disk). Is it a bug? Or maybe it is possible to change the instance flavor extra spec? -- Cheers, Roman Dobosz

3 6

[oslo] Berlin Summit Recap
by Ben Nemec 03 Dec '18

03 Dec '18

A bit late because I was on PTO the week after and it turns out I had a lot more to say than I realized. :-) There wasn't a ton of Oslo stuff going on, but there were a few interesting things that I discuss in [1]. I also ended up writing my thoughts about some non-Oslo-specific sessions I attended, including one that I split off in its own post because it got a bit long and deserved standalone attention[2]. 1: http://blog.nemebean.com/content/berlin-summit-recap 2: http://blog.nemebean.com/content/upstream-openstack-performance-and-release… -Ben

1 0