April 2019 - openstack-discuss - lists.openstack.org

Announcing Gertty 1.6.0
by corvus＠inaugust.com 24 Apr '19

24 Apr '19

Announcing Gertty 1.6.0 ======================= Gertty is a console-based interface to the Gerrit Code Review system. Gertty is designed to support a workflow similar to reading network news or mail. It syncs information from Gerrit to local storage to support disconnected operation and easy manipulation of local git repos. It is fast and efficient at dealing with large numbers of changes and projects. The full README may be found here: https://opendev.org/ttygroup/gertty/src/branch/master/README.rst Changes since 1.5.0: ==================== * The default config file location is now ~/.config/gertty/gertty.yaml (but Gertty will fall back on the previous default of ~/.gertty.yaml if it is not found) * The source code is now hosted in OpenDev (https://opendev.org) * Gertty supports (and should be run with) python3 * Added tab display support * Reviewkeys are enabled in diffs * Added a new option (off by default) to close the change after reviewing * Added inline comments to the change overview screen * The size column graph is more configurable * Reviewkeys now support sending a message * Added more example configurations As well as several bug fixes and stability improvements. Thanks to the following people whose changes are included in this release: Clint Byrum Dominique Martinet Doug Wiegley Emilien Macchi Ian Wienand John L. Villalovos Logan V Major Hayden Masayuki Igawa Matthias Runge Natal Ngétal Nate Johnston Nguyen Hung Phuong Robert Collins Tobias Henkel Tristan Cacqueray

1 0

[First Contact] [SIG] [PTL] Project Liaisons Update
by Matthew Oliver 24 Apr '19

24 Apr '19

Hey PTLs, Now that the new PTL election season is over and you all should be coming to grips with your life choices. It's time to update the First contact project liaison list[0]. What are first contact liaisons do I hear you ask? We at the first contact SIG strive to be a point of call for new contributors. When they do contact or we find a new contributors first patch, we try and connect them with the project. This could be as simple a adding the liaison to the review or providing and introduction. Anyone can be a liaison for a project, so you're welcome to delegate, however we do default to PTLs. Further given that we live on a globe, tracking and having multiple liaisons on each project from different timezones would also be a big win. For those of you who have already delegated previously and/or are continuing to PTL, you don't get off too easily. The world has finished it's summertime/daylight saving dance, so is time to update your timezone's too. I know the summit/PTG is just around the corner, so while your updating your etherpad and wiki's what's one more ;) Regards, Matt [0] https://wiki.openstack.org/wiki/First_Contact_SIG#Project_Liaisons

1 0

The python black project.
by Natal Ngétal 24 Apr '19

24 Apr '19

Hi everyone, Black is project to format Python code. It's more and more used by the python community. That can save time and harmonize the code. For example, simple quote versus double quote, that was not checked by pep8.i It's just an example of what make black With a pre-hook commit hook this will be also avoid to lose time with pep8 errors. Two links to see more: https://github.com/ambv/black https://www.mattlayman.com/blog/2018/python-code-black/ I think it can be very interesting to start to use Black on OpenStack. What do you thinks about that? For example, we can introduce it on some projects, I would volunteer to try on TripleO. My best regards

21 46

[openstack-dev] [neutron] Cancelling the L3 meeting on April 24
by Miguel Lavalle 24 Apr '19

24 Apr '19

Hi Neutrinos, Since we are meeting next week in Denver to discuss, among other things, L3 topics, we are cancelling this week's meeting. Safe travels to everybody! Miguel

1 0

[nova][ptg] Draft Agenda
by Eric Fried 24 Apr '19

24 Apr '19

Nova PTGers- I have drafted an agenda at the bottom of the main etherpad [1]. It is subject to change for the next week for various reasons, but I expect mainly a) for scheduling conflicts and the like (see below) and b) things falling off because resolved (e.g. I expect the SEV spec to merge in the next couple of days). Please review the agenda, **especially if your schedule isn't "I'm present all three days, and glued to the nova team"** and contact me [2] if you: - have a scheduling conflict for a topic you own **or** a topic you care about and want to be present for. - feel I've prioritized your topic unjustly. - feel I've allocated too little or too much time [3] to your topic. - think I've committed some other glaring error or omission. Because we're short on time, I'll be strict about sticking to the schedule in whatever form it solidifies into. I've allocated some time at the end [4] to resume discussions that have to be chopped off early as a result. Thanks, efried P.S. Please be gentle with me. I've tried to be fair, accommodate scheduling issues I know about, and allocate reasonable chunks of time for topics even when I barely understand them. If I've made a mistake, assume it's out of ignorance, not malice or prejudice. [1] https://etherpad.openstack.org/p/nova-ptg-train [2] via email or IRC. Please do not edit the agenda on the etherpad. [3] seriously, including "we don't actually need to talk about this at the PTG". [4] I know it sucks that it's on Saturday afternoon; my working theory is that that's better than some topics not getting any floor time at all.

1 0

Openstack LXC
by Alejandro Ruiz Bermejo 24 Apr '19

24 Apr '19

Hi everyone, I have a fresh Openstack installation and i need to use LXC to launch instances I made the deployment manually, currently i have one controller node, one compute node, one block storage node and one object storage node. I already made the necessary configurations in the nova.conf file as appears on the official documentation site compute_driver = libvirt.LibvirtDriver [libvirt]virt_type = lxc and i have installed the nova-compute-lxc package and the nbd-server package. i created a new ubuntu 18 image for the container with the following command: openstack image create --public --container-format=bare --disk-format=raw --file bionic-server-cloudimg-amd64.tar.gz ubuntu18 and the flavor: openstack flavor create --ram 2048 --vcpus 1 --disk 5 lxc.test then when i try to launch an instance: openstack server create --flavor lxc.test --image ubuntu18 --nic net-id=d0f6cc99-565b-484f-a5ab-fcb1c3af456d --security-group 1160755e-1312-43c6-8ebb-b12b92d35e51 --key-name mykey lxc6 I get the following Error cat /var/log/nova/nova-*.log | grep 269d2480-4477-4382-b09c-9c686ab7a17c 2019-04-23 17:59:26.846 3949 INFO nova.osapi_compute.wsgi.server [req-1dbeb432-67f0-4305-b91c-6548dde49bee a16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 - default default] 10.8.9.54 "GET /v2.1/servers/269d2480-4477-4382-b09c-9c686ab7a17c HTTP/1.1" status: 200 len: 1737 time: 0.6656921 2019-04-23 17:59:33.076 3944 INFO nova.api.openstack.compute.server_external_events [req-206e8ace-90e3-4a95-8274-4a9091c174c0 c2657fa5083f4d5c932d53d6bf094604 18337c70d397424f8895cd4f1ae7450e - default default] Creating event network-changed:818d6adc-252e-4d47-9275-009cff55c716 for instance 269d2480-4477-4382-b09c-9c686ab7a17c on compute 2019-04-23 17:59:37.663 3926 *ERROR* nova.scheduler.utils [req-abd32ef2-3a19-4154-a7da-893f3d2b2aef a16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 - default default] [instance: 269d2480-4477-4382-b09c-9c686ab7a17c] Error from last host: compute (node compute.cujae.edu.cu): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1841, in _do_build_and_run_instance\n filter_properties, request_spec)\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2121, in _build_and_run_instance\n instance_uuid=instance.uuid, reason=six.text_type(e))\n', u'RescheduledException: Build of instance 269d2480-4477-4382-b09c-9c686ab7a17c was re-scheduled: mount() takes exactly 4 arguments (3 given)\n'] Is this error a bug or something fixable?? Has anyone accomplished this kind of environment or used lxc without problems?

3 4

[keystone] No meeting next two weeks
by Colleen Murphy 23 Apr '19

23 Apr '19

As discussed in today's meeting[1], we'll be cancelling next week's meeting (30 April) due to the summit, as well as the following week's meeting (7 May) for recovery. Colleen [1] http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-04-23-1…

1 0

[Security][Security SIG] Weekly Meeting Schedule
by Gage Hugo 23 Apr '19

23 Apr '19

With the Summit/PTG next week, the Security SIG meeting for May 2nd will be cancelled due to people attending the Summit/PTG. The following week I will not be available to chair, so the meeting for May 9th will be preemptively canceled, however if there is a need for discussion, please feel free to host at the usual time. We will be back to regularly scheduled meetings again on the 16th, Safe travels everyone attending the Summit/PTG!

1 0

[Security][Security SIG] Weekly Meeting Schedule
by Gage Hugo 23 Apr '19

23 Apr '19

With the Summit/PTG next week, the Security SIG meeting for May 2nd will be cancelled due to people attending the Summit/PTG. The following week I will not be available to chair, so the meeting for May 9th will be preemptively canceled, however if there is a need for discussion, please feel free to host at the usual time. We will be back to regularly scheduled meetings again on the 16th, Safe travels everyone attending the Summit/PTG! - Gage

1 0

[dev] oslosphinx Sphinx theme is EOL
by Stephen Finucane 23 Apr '19

23 Apr '19

Just a quick pointer that the oslosphinx theme does not work with Sphinx 2.0, which was released yesterday, failing with the following error: Exception occurred: File "/home/zuul/src/git.openstack.org/openstack/nova-specs/.tox/docs/lib/python3.6/site-packages/oslosphinx/__init__.py", line 76, in builder_inited app.info('Using openstack theme from %s' % theme_dir) AttributeError: 'Sphinx' object has no attribute 'info' The oslo team have decided not to fix these issues, given that oslosphinx is EOL since Pike, and we suggest that people instead migrate to openstackdocstheme [1] (for projects that are able to use the OpenStack brand [2]) or something else (for projects that are not). For the former, I suggest follow the openstackdocstheme [1] or look at what we've done in nova-specs [3] for an existing example. If you have issues, please reach out on #openstack-doc and one of us will try our best to help you migrate. I'll work with infra to get the repo shuttered and avoid any further confusion with this theme going forward. Stephen [1] https://docs.openstack.org/openstackdocstheme/latest/ [2] https://www.openstack.org/brand [3] https://review.openstack.org/#/c/648670/

1 1