[openstack-dev] [Searchlight] Report for the week of Stein R-22

[Trinh Nguyen]

Hi team,

This is the report for last week, Stein R-22 [1]. Please follow to know
what going on with Searchlight.

[1]
https://www.dangtrinh.com/2018/11/searchlight-weekly-report-stein-r-22.html

Bests,

-- 
*Trinh Nguyen*
*www.edlab.xyz *
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo][openstack-ansible] Updates on collaboration on os_tempest role

[Chandan kumar]

Hello,

During the starting of Denver 2018 PTG [1]., We started collaborating
towards using the
openstack-ansible-os_tempest role [2] as a unified tempest role in TripleO and
openstack-ansible project within OpenStack community.

It will help us to improve the testing strategies between two projects
which can be
further expanded to other OpenStack deployment tools.

We will be sharing bi-weekly updates through mailing lists.
We are tracking/planning all the work here:
Proposal doc: https://etherpad.openstack.org/p/ansible-tempest-role
Work item collaboration doc:
https://etherpad.openstack.org/p/openstack-ansible-tempest

Here is the update till now:
openstack-ansible-os_tempest project:

* Enable stackviz support - https://review.openstack.org/603100
* Added support for installing tempest from distro -
https://review.openstack.org/591424
* Fixed missing ; from if statement in tempest_run -
https://review.openstack.org/614521
* Added task to list tempest plugins - https://review.openstack.org/615837
* Remove apt_package_pinning dependency from os_tempest role -
https://review.openstack.org/609992
* Enable python-tempestconf support - https://review.openstack.org/612968

Support added to openstack/rpm-packaging project (will be consumed in
os_tempest role):
* Added spec file for stackviz - https://review.openstack.org/609337
* Add initial spec for python-tempestconf - https://review.openstack.org/598143

Upcoming improvements:
* Finish the integration of python-tempestconf in os_tempest role.

Have queries, Feel free to ping us on #tripleo or #openstack-ansible channel.

Links:
[1.] http://lists.openstack.org/pipermail/openstack-dev/2018-August/133119.html
[2.] http://git.openstack.org/cgit/openstack/openstack-ansible-os_tempest

Thanks,

Chandan Kumar

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] puppet5 has broken the master gate

[Alex Schultz]

Just a heads up but we recently updated to puppet5 in the master
dependencies. It appears that this has completely hosed the master
scenarios and containers-multinode jobs.  Please do recheck/approve
anything until we get this resolved.

See https://bugs.launchpad.net/tripleo/+bug/1803024

I have a possible fix (https://review.openstack.org/#/c/617441/) but
it's probably a better idea to roll back the puppet package if
possible.

Thanks,
-Alex

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][neutron] boot server with more than one subnet selection question

[Chen CH Ji]

Got it, this is what I am looking for .. thank you
 
- Original message -From: Slawomir Kaplonski To: "OpenStack Development Mailing List (not for usage questions)" Cc:Subject: Re: [openstack-dev] [nova][neutron] boot server with more than one subnet selection questionDate: Tue, Nov 13, 2018 1:06 AM 
Hi,You can choose which subnet (and even IP address) should be used, see „fixed_ips” field in [1].If You will not provide anything Neutron will choose for You one IPv4 address and one IPv6 address and in both cases it will be chosen randomly from available IPs from all subnets.[1] https://developer.openstack.org/api-ref/network/v2/?expanded=create-port-detail#create-port> Wiadomość napisana przez Chen CH Ji  w dniu 12.11.2018, o godz. 13:44:>> I have a network created like below:>  > 1 network with 3 subnets (1 ipv6 and 2 ipv4) ,when boot, whether I can select subnet to boot from or the subnet will be force selected by the order the subnet created? Any document or code can be  referred? Thanks>  > | fd0e2078-044d-4c5c-b114-3858631e6328 | private   | a8184e4f-5165-4ea8-8ed8-b776d619af6e fd9b:c245:1aaa::/64 |> |                                      |           | b3ee7cad-c672-4172-a183-8e9f069bea31 10.0.0.0/26         |> |                                      |           | 9439abfd-afa2-4264-8422-977d725a7166 10.0.2.0/24         |>  >> __> OpenStack Development Mailing List (not for usage questions)> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev—Slawek KaplonskiSenior software engineerRed Hat__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [masakari] No masakari meeting on 11/12

[Sam P]

Hi all!,
 Sorry for the late announcement. Since most of us in Berlin summit,
there will be no IRC meeting at 11/12.

--- Regards,
Sampath

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [heat] Heat sessions & forum in Berlin Summit

[Rico Lin]

Dear all
Here are some Heat relative sessions in OpenStack summit for you this week.
Welcome everyone to join us and check it out!

*Orchestration Ops/Users feedback session*
Wed 14, 1:40pm - 2:20pm
CityCube Berlin - Level 3 - M-Räume 6
https://etherpad.openstack.org/p/heat-user-berlin

*Heat - Project Update*
Wed 14, 3:45pm - 4:05pm
CityCube Berlin - Level 3 - M-Räume 3
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22739/heat-project-update

*Autoscaling Integration, improvement, and feedback*
Thu 15, 9:00am - 9:40am
CityCube Berlin - Level 3 - M-Räume 8
https://etherpad.openstack.org/p/autoscaling-integration-and-feedback

*Heat - Project Onboarding*
Thu 15, 10:50am - 11:30am
CityCube Berlin - Level 3 - M-Räume 1
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22733/heat-project-onboarding


-- 
May The Force of OpenStack Be With You,

*Rico Lin*irc: ricolin
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cinder] No meeting this week ...

[Jay S Bryant]

Team,

Just a friendly reminder that we will not have our weekly meeting this 
week due to the OpenStack Summit.


Hope to see some of you here.  Otherwise, talk to you next week!

Thanks,

Jay


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla][iconic] baremetal network

[Mark Goddard]

Hi Manuel,

You can configure the neutron tenant network types in kolla-ansible via the
'neutron_tenant_network_types' variable in globals.yml. It's a
comma-separated list. The default for that variable is vxlan, it's expected
that you set it to match your requirements.

The 'ironic_cleaning_network' variable should be the name of a network in
neutron to be used for cleaning, rather than an interface name. If you're
using flat networking, this will just be 'the' network.

Regards,
Mark

On Mon, 12 Nov 2018 at 01:23, Manuel Sopena Ballesteros <
manuel...@garvan.org.au> wrote:

> Dear Kolla-ansible team,
>
>
>
> I am trying to deploy ironic through kolla-ansible. According to ironic
> documentation
> https://docs.openstack.org/ironic/rocky/install/configure-networking.html
> we need bare metal network with tenant_network_types = flat. However
> kolla-ansible configures:
>
>
>
> [root@TEST-openstack-controller ~]# grep -R -i "baremetal" -R /etc/kolla/*
>
> /etc/kolla/neutron-openvswitch-agent/ml2_conf.ini:mechanism_drivers =
> openvswitch,baremetal,l2population
>
> /etc/kolla/neutron-server/ml2_conf.ini:mechanism_drivers =
> openvswitch,baremetal,l2population
>
>
>
>
>
> [root@TEST-openstack-controller ~]# grep -R -i "tenant_network_types" -R
> /etc/kolla/*
>
> /etc/kolla/neutron-openvswitch-agent/ml2_conf.ini:tenant_network_types =
> vxlan
>
> /etc/kolla/neutron-server/ml2_conf.ini:tenant_network_types = vxlan
>
>
>
> This is my filtered globals.yml:
>
>
>
> [root@openstack-deployment ~]# grep -E -i "(^[^#]|ironic)"
> /etc/kolla/globals.yml
>
> ---
>
> openstack_release: "rocky"
>
> kolla_internal_vip_address: "192.168.1.51"
>
> neutron_external_interface: "ens161"
>
> enable_cinder: "yes"
>
> enable_cinder_backend_nfs: "yes"
>
> #enable_horizon_ironic: "{{ enable_ironic | bool }}"
>
> enable_ironic: "yes"
>
> #enable_ironic_ipxe: "no"
>
> #enable_ironic_neutron_agent: "no"
>
> #enable_ironic_pxe_uefi: "no"
>
> glance_enable_rolling_upgrade: "no"
>
> # Ironic options
>
> # following value must be set when enable ironic, the value format
>
> ironic_dnsmasq_dhcp_range: "192.168.1.100,192.168.1.150"
>
> # PXE bootloader file for Ironic Inspector, relative to /tftpboot.
>
> ironic_dnsmasq_boot_file: "pxelinux.0"
>
> ironic_cleaning_network: "ens224"
>
> #ironic_dnsmasq_default_gateway: 192.168.1.255
>
> # Configure ironic upgrade option, due to currently kolla support
>
> # two upgrade ways for ironic: legacy_upgrade and rolling_upgrade
>
> # The variable "ironic_enable_rolling_upgrade: yes" is meaning
> legacy_upgrade
>
> #ironic_enable_rolling_upgrade: "yes"
>
> #ironic_inspector_kernel_cmdline_extras: []
>
> tempest_image_id:
>
> tempest_flavor_ref_id:
>
> tempest_public_network_id:
>
> tempest_floating_network_name:
>
>
>
> ens224 is a my management network for admins to ssh and install and manage
> the physical nodes.
>
>
>
> Any idea why tenant_network_types = vxlan and not flat as suggested by
> the ironic documentation?
>
>
>
> Thank you
>
>
>
> *Manuel Sopena Ballesteros *| Big data Engineer
> *Garvan Institute of Medical Research *
> The Kinghorn Cancer Centre, 370 Victoria Street, Darlinghurst, NSW 2010
> *T:* + 61 (0)2 9355 5760 | *F:* +61 (0)2 9295 8507 | *E:*
> manuel...@garvan.org.au
>
>
> NOTICE
> Please consider the environment before printing this email. This message
> and any attachments are intended for the addressee named and may contain
> legally privileged/confidential/copyright information. If you are not the
> intended recipient, you should not read, use, disclose, copy or distribute
> this communication. If you have received this message in error please
> notify us at once by return email and then delete both messages. We accept
> no liability for the distribution of viruses or similar in electronic
> communications. This notice should not be removed.
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [neutron] Cancelling weekly meeting on November 12th

[Miguel Lavalle]

Dear Neutron Team,

Due to the OpenStack Summit in Berlin and the activities around it, let's
cancel the weekly IRC meeting on November 12th. We will resume normally on
the 20th.

Best regards

Miguel
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cinder][manila] Cinder and Friends Dinner at Berlin Summit ...

[Jay S Bryant]

Ivan,

Yeah, I saw that was the case but it seems like there is not a point in 
time where there isn't a conflict.  Need to get some food at some point 
so anyone who wants to join can, and then we can head to the party if 
people want.


Jay


On 11/10/2018 8:07 AM, Ivan Kolodyazhny wrote:

Thanks for organizing this, Jay,

Just in case if you missed it, Matrix Party hosted by Trilio + Red Hat 
will be on Tuesday too.



Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/


On Thu, Nov 8, 2018 at 12:43 AM Jay S Bryant > wrote:


All,

I am working on scheduling a dinner for the Cinder team (and our
extended family that work on and around Cinder) during the Summit
in Berlin.  I have created an etherpad for people to RSVP for
dinner [1].

It seemed like Tuesday night after the Marketplace Mixer was the
best time for most people.

So, it will be a little later dinner ... 8 pm.  Here is the place:

Location: http://www.dicke-wirtin.de/
Address: Carmerstraße 9, 10623 Berlin, Germany

It looks like the kind of place that will fit for our usual group.

If planning to attend please add your name to the etherpad and I
will get a reservation in over the weekend.

Hope to see you all on Tuesday!

Jay

[1] https://etherpad.openstack.org/p/BER-cinder-outing-planning

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [openstack-ansible] meeting cancelled

[Mohammed Naser]

Hi everyone,

Due to most of us being at the OpenStack Summit, we're cancelling the
meeting tomorrow.

Thanks everyone and see you in Berlin.

Regards,
Mohammed

-- 
Mohammed Naser — vexxhost
-
D. 514-316-8872
D. 800-910-1726 ext. 200
E. mna...@vexxhost.com
W. http://vexxhost.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] Meetings cancelled this and next week - resumes November 26th

[Julia Kreger]

Greetings everyone!

We're cancelling this week's meeting and next week's meeting due to the
OpenStack Summit and US holidays the following week where some of our core
reviewers will also be on vacation.

If there are any questions, please feel to ask in #openstack-ironic.

See  you all in IRC.

-Julia
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] puppet5 has broken the master gate

[Chandan kumar]

Hello Alex,

On Tue, Nov 13, 2018 at 9:53 AM Alex Schultz  wrote:
>
> Just a heads up but we recently updated to puppet5 in the master
> dependencies. It appears that this has completely hosed the master
> scenarios and containers-multinode jobs.  Please do recheck/approve
> anything until we get this resolved.
>
> See https://bugs.launchpad.net/tripleo/+bug/1803024
>
> I have a possible fix (https://review.openstack.org/#/c/617441/) but
> it's probably a better idea to roll back the puppet package if
> possible.
>

In RDO, we have reverted Revert "Stein: push puppet 5.5.6" ->
https://review.rdoproject.org/r/#/c/17333/1

Thanks for the heads up!

Thanks,

Chandan Kumar

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova][neutron] boot server with more than one subnet selection question

[Chen CH Ji]

I have a network created like below:
 
1 network with 3 subnets (1 ipv6 and 2 ipv4) ,when boot, whether I can select subnet to boot from or the subnet will be force selected by the order the subnet created? Any document or code can be  referred? Thanks
 
| fd0e2078-044d-4c5c-b114-3858631e6328 | private   | a8184e4f-5165-4ea8-8ed8-b776d619af6e fd9b:c245:1aaa::/64 ||  |   | b3ee7cad-c672-4172-a183-8e9f069bea31 10.0.0.0/26 ||  |   | 9439abfd-afa2-4264-8422-977d725a7166 10.0.2.0/24 |
 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [docs] New Four Opens Project

[Chris Hoge]

Earlier this year, the OpenStack Foundation staff had the opportunity to 
brainstorm some ideas about how to express the values behind The Four Opens and 
how they are applied in practice. As the Foundation grows in scope to include 
new strategic focus areas and new projects, we felt it was important to provide 
explanation and guidance on the principles that guide our community.

We’ve collected these notes and have written some seeds to start this document. 
I’ve staged this work into github and have prepared a review to move the work 
into OpenStack hosting, turning this over to the community to help guide and 
shape the document.

This is very much a work in progress, but we have a goal to polish this up and 
make it an important document that captures our vision and values for the 
OpenStack development community, guides the establishment of governance for new 
top-level projects, and is a reference for the open-source development 
community as a whole.

I also want to be clear that the original Four Opens, as listed in the 
OpenStack governance page, is an OpenStack TC document. This project doesn’t 
change that. Instead, it is meant to be applied to the Foundation as a whole 
and be a reference to the new projects that land both as pilot top-level 
projects and projects hosted by our new infrastructure efforts.

Thanks to all of the original authors of the Four-Opens for your visionary work 
that started this process, and thanks in advance to the community members who 
will continue to grow and evolve this document.

Chris Hoge
OpenStack Foundation

Four Opens: https://governance.openstack.org/tc/reference/opens.html
New Project Review Patch: https://review.openstack.org/#/c/617005/
Four Opens Document Staging: https://github.com/hogepodge/four-opens

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][neutron] boot server with more than one subnet selection question

[Slawomir Kaplonski]

Hi,

You can choose which subnet (and even IP address) should be used, see 
„fixed_ips” field in [1].
If You will not provide anything Neutron will choose for You one IPv4 address 
and one IPv6 address and in both cases it will be chosen randomly from 
available IPs from all subnets.

[1] 
https://developer.openstack.org/api-ref/network/v2/?expanded=create-port-detail#create-port

> Wiadomość napisana przez Chen CH Ji  w dniu 12.11.2018, 
> o godz. 13:44:
> 
> I have a network created like below:
>  
> 1 network with 3 subnets (1 ipv6 and 2 ipv4) ,when boot, whether I can select 
> subnet to boot from or the subnet will be force selected by the order the 
> subnet created? Any document or code can be  referred? Thanks
>  
> | fd0e2078-044d-4c5c-b114-3858631e6328 | private   | 
> a8184e4f-5165-4ea8-8ed8-b776d619af6e fd9b:c245:1aaa::/64 |
> |  |   | 
> b3ee7cad-c672-4172-a183-8e9f069bea31 10.0.0.0/26 |
> |  |   | 
> 9439abfd-afa2-4264-8422-977d725a7166 10.0.2.0/24 |
>  
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

— 
Slawek Kaplonski
Senior software engineer
Red Hat


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [qa] [containers] [airship] [berlin] Berlin Airship Forums

[MCEUEN, MATT]

I wanted to make sure that all interested folks are aware of the 
Airship-related Forums that will be held on Tuesday:

Cross-project container security discussion:
  https://etherpad.openstack.org/p/BER-container-security
Airship Quality Assurance use cases:
https://etherpad.openstack.org/p/BER-airship-qa
Airship Bare Metal provisioning brainstorming & design:
https://etherpad.openstack.org/p/BER-airship-bare-metal

We welcome all participation and discussion - please add any topics you'd like 
to discuss to the etherpads!

I look forward to some good sessions tomorrow.
Thanks,
Matt

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev