Re: [openstack-dev] [all][tc][release][election][adjutant] Welcome Adjutant as an official project!
On Tue, Jul 17, 2018 at 01:52:39PM -0400, Doug Hellmann wrote: > The Adjutant team's application [1] to become an official project > has been approved. Welcome! > > As I said on the review, because it is past the deadline for Rocky > membership, Adjutant will not be considered part of the Rocky > release, but a future release can be part of Stein. > > The team should complete the onboarding process for new projects, > including holding PTL elections for Stein, Now would be a good time to do this :) See: https://governance.openstack.org/election/#how-to-submit-a-candidacy for details Yours Tony. signature.asc Description: PGP signature __ 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] network isolation can't find files referred to on director
Hi,
With my nic configs I get the following error
2018-07-26 16:42:49Z [overcloud.ComputeGammaV3.0.NetworkConfig]:
CREATE_FAILED resources.NetworkConfig: Parameter
'InternalApiNetworkVlanID' is invalid: could not convert string to float:
2018-07-26 16:42:49Z [overcloud.ComputeGammaV3.0]: CREATE_FAILED Resource
CREATE failed: resources.NetworkConfig: Parameter
'InternalApiNetworkVlanID' is invalid: could not convert string to float:
2018-07-26 16:42:50Z [overcloud.ComputeGammaV3.0]: CREATE_FAILED
resources.NetworkConfig: resources[0].Parameter 'InternalApiNetworkVlanID'
is invalid: could not convert string to float:
2018-07-26 16:42:50Z [overcloud.ComputeGammaV3]: UPDATE_FAILED Resource
CREATE failed: resources.NetworkConfig: resources[0].Parameter
'InternalApiNetworkVlanID' is invalid: could not convert string to float:
2018-07-26 16:42:51Z [overcloud.ComputeGammaV3]: CREATE_FAILED
resources.ComputeGammaV3: Resource CREATE failed: resources.NetworkConfig:
resources[0].Parameter 'InternalApiNetworkVlanID' is invalid: could not
convert string to float:
2018-07-26 16:42:51Z [overcloud]: CREATE_FAILED Resource CREATE failed:
resources.ComputeGammaV3: Resource CREATE failed: resources.NetworkConfig:
resources[0].Parameter 'InternalApiNetworkVlanID' is invalid: could not
convert string to float:
2018-07-26 16:42:51Z [overcloud.ComputeGammaV3.0.NetIpMap]:
CREATE_COMPLETE state changed
Stack overcloud CREATE_FAILED
overcloud.ComputeGammaV3.0.NetworkConfig:
resource_type: OS::TripleO::ComputeGammaV3::Net::SoftwareConfig
physical_resource_id:
status: CREATE_FAILED
status_reason: |
resources.NetworkConfig: Parameter 'InternalApiNetworkVlanID' is
invalid: could not convert string to float:
Heat Stack create failed.
Heat Stack create failed.
(undercloud) [stack@staging-director ~]$ packet_write_wait: Connection to
192.168.50.30 port 22: Broken pipe
The parameter is defined as following in nic config file
InternalApiNetworkVlanID:
default: ''
description: Vlan ID for the internal_api network traffic.
type: number
I worked fine when I was using RHOSP11(Ocata)
The custom_network_data.yaml defines the internal network as following
- name: InternalApi
name_lower: internal_api
vip: true
vlan: 711
ip_subnet: '172.16.2.0/24'
allocation_pools: [{'start': '172.16.2.4', 'end': '172.16.2.250'}]
Samuel
On Fri, Jul 27, 2018 at 7:41 PM, James Slagle
wrote:
> On Thu, Jul 26, 2018 at 4:58 AM, Samuel Monderer
> wrote:
> > Hi James,
> >
> > I understand the network-environment.yaml will also be generated.
> > What do you mean by rendered path? Will it be
> > "usr/share/openstack-tripleo-heat-templates/network/ports/"?
>
> Yes, the rendered path is the path that the jinja2 templating process
> creates.
>
> > By the way I didn't find any other place in my templates where I refer to
> > these files?
> > What about custom nic configs is there also a jinja2 process to create
> them?
>
> No. custom nic configs are by definition, custom to the environment
> you are deploying. Only you know how to properly define what newtork
> configurations needs applying.
>
> Our sample nic configs are generated from jinja2 now. For example:
> tripleo-heat-templates/network/config/single-nic-vlans/role.role.j2.yaml
>
> If you wanted to follow that pattern such that your custom nic config
> templates were generated, you could do that
>
__
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] [charms] PTL candidacy for Stein cycle
Hello all, I hereby announce my candidacy for PTL of the OpenStack Charms project [0]. Through the course of the past two years I have made many contributions to the Charms projects and I have had the privilege of becoming a Core developer. Prior to focusing on the Charms project I have made upstream contributions in other OpenStack projects and I have followed the unfolding and development of the OpenStack community with great interest. We live in exciting times and I believe great things are afoot for OpenStack as a stable, versatile and solid contender in the cloud space. It would be my privilege to be able to help further that along as PTL for the Charms project. Our project has a strong and disperse group of contributors and we are blessed with motivated and assertive people taking interest in maintaining existing code as well as developing new features. The most important aspect of my job as PTL will be to make sure we maintain room for the diversity of contributions without losing velocity and direction. Maintaining and developing our connection with the broader OpenStack community will also be of great importance. Some key areas of focus for Stein cycle: - Python 3 migration - The clock is ticking for Python 2 and we need to continue the drive towards porting all our code to Python 3 - Continue modernization of test framework - Sustained software quality is only as good as you can prove through the quality of your unit and functional tests. - Great progress has been made this past cycle in developing and extending functionality of a new framework for our functional tests and we need to continue this work. - Continue to build test driven development culture, and export this culture to contributors outside the core team. - [Multi-cycle] Explore possibilities and methodologies for Classic -> layered Reactive Charm migrations - A lot of effort has been put into the Reactive Charm framework and the reality of writing a new Charm today is quite different from what it was just a few years ago. - The time and effort needed to maintain a layered Reactive Charm is also far less than what it takes to maintain a classic Charm. - There are many hard and difficult topics surrounding such a migration but I think it is worth spending some time exploring our options of how we could get there. - Evaluate use of upstream release tools - The OpenStack release team has put together some great tools that might make our release duties easier. Let us evaluate adopting some of them for our project. 0: https://review.openstack.org/#/c/586821/ -- Frode Nordahl (IRC: fnordahl) __ 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
