[Openstack] Certifying SDKs

[Melvin Hillsman]

Hey everyone,

On the path to potentially certifying SDKs we would like to gather a list
of scenarios folks would like to see "guaranteed" by an SDK.

Some examples - boot instance from image, boot instance from volume, attach
volume to instance, reboot instance; very much like InterOp works to ensure
OpenStack clouds provide specific functionality.

Here is a document we can share to do this -
https://docs.google.com/spreadsheets/d/1cdzFeV5I4Wk9FK57yqQmp5JJdGfKzEOdB3Vtt9vnVJM/edit#gid=0

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] Certifying SDKs

[Melvin Hillsman]

Hey everyone,

On the path to potentially certifying SDKs we would like to gather a list
of scenarios folks would like to see "guaranteed" by an SDK.

Some examples - boot instance from image, boot instance from volume, attach
volume to instance, reboot instance; very much like InterOp works to ensure
OpenStack clouds provide specific functionality.

Here is a document we can share to do this -
https://docs.google.com/spreadsheets/d/1cdzFeV5I4Wk9FK57yqQmp5JJdGfKzEOdB3Vtt9vnVJM/edit#gid=0

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[openstack-dev] [nova]VolumeNotCreated: Volume did not finish being created even after we waited 12 seconds or 5 attempts. And its status is error.

[李杰]

Hi,all:
Now I boot a volume-backed instance,and set" 
block_device_allocate_retries=120 " ,but the result is still is volume did not 
finish being created.Can you give me some advice?Help in troubleshooting this 
issue will be appreciated.






Best Regards
Lijie__
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] [OpenStack][Takcer] SSL error while connecting tacker to OpenStack VIM

[Amit Kumar]

Hi All,

We are trying to use tacker for network service orchestration, but we are
stuck at the initial steps only. We have installed OpenStack Ocata using
OpenStack-Ansible and Tacker using DevStack on a virtual machine, other
than OpenStack Controller.

We are connecting to OpenStack VIM using the following command:
*tacker --debug vim-register  --description 'OpenStack Ocata' --config-file
vim_config.yaml Site1*

On running the above command, we are getting the following error:

*ERROR: tackerclient.shell An SSL error occurred.*
*Traceback (most recent call last):*
*  File "/usr/local/lib/python2.7/dist-packages/tackerclient/shell.py",
line 593, in run_subcommand*
*return run_command(cmd, cmd_parser, sub_argv)*
*  File "/usr/local/lib/python2.7/dist-packages/tackerclient/shell.py",
line 74, in run_command*
*return cmd.run(known_args)*
*  File
"/usr/local/lib/python2.7/dist-packages/tackerclient/common/command.py",
line 29, in run*
*return super(OpenStackCommand, self).run(parsed_args)*
*  File "/usr/local/lib/python2.7/dist-packages/cliff/display.py", line
112, in run*
*column_names, data = self.take_action(parsed_args)*
*  File
"/usr/local/lib/python2.7/dist-packages/tackerclient/common/command.py",
line 35, in take_action*
*return self.get_data(parsed_args)*
*  File
"/usr/local/lib/python2.7/dist-packages/tackerclient/tacker/v1_0/__init__.py",
line 441, in get_data*
*data = obj_creator(body)*
*  File
"/usr/local/lib/python2.7/dist-packages/tackerclient/v1_0/client.py", line
100, in with_params*
*ret = self.function(instance, *args, **kwargs)*
*  File
"/usr/local/lib/python2.7/dist-packages/tackerclient/v1_0/client.py", line
460, in create_vim*
*return self.post(self.vims_path, body=body)*
*  File
"/usr/local/lib/python2.7/dist-packages/tackerclient/v1_0/client.py", line
296, in post*
*headers=headers, params=params)*
*  File
"/usr/local/lib/python2.7/dist-packages/tackerclient/v1_0/client.py", line
209, in do_request*
*self._handle_fault_response(status_code, replybody)*
*  File
"/usr/local/lib/python2.7/dist-packages/tackerclient/v1_0/client.py", line
183, in _handle_fault_response*
*exception_handler_v10(status_code, des_error_body)*
*  File
"/usr/local/lib/python2.7/dist-packages/tackerclient/v1_0/client.py", line
68, in exception_handler_v10*
*status_code=status_code)*
*InternalServerError: An SSL error occurred.*

Contents of vim_config.yaml are:

*auth_url: 'https://192.168.255.45:5000/v3/
'*
*username: 'admin'*
*password: '56d1bcb5f554830270eeb9a6c1950728fb3f3'*
*project_name: 'admin'*
*project_domain_name: 'Default'*
*user_domain_name: 'Default'*

Please suggest if you have faced similar problem and if there is any
solution to this.

In addition to this, we also tried another OpenStack setup which was
allowing external endpoint on http, instead of https, and registration to
it was successful.

Regards,
Amit
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[openstack-dev] [glance] priorities for the week (12/08-12/14)

[Brian Rosmaita]

Let's get the scrubber refactor and anything that got postponed from
Q-2 merged before the meeting on Thursday.

scrubber:
https://review.openstack.org/#/c/510449/ (time zone bug has been addressed)

others:
https://review.openstack.org/#/c/524060/
https://review.openstack.org/#/c/521457/
https://review.openstack.org/#/c/523029/
https://review.openstack.org/#/c/523028/
https://review.openstack.org/#/c/523179/

Have a productive week!
brian

__
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][cinder] Nova is now using the Cinder volume attachments API - multiattach comes next

[Ildiko Vancsa]

Thanks Matt for all the help so far and also for taking the time to write up 
this summary! I would like to join in saying thanks to the handful of people 
listed below who formed an amazing cross-project team during the past two years.

I strongly believe that by hunting for multi-attach support we stepped on the 
right track in terms of the interactions between the API’s of Cinder and Nova 
and better readability and maintainability of the code base in both projects on 
the long run with the changes we’ve made so far.

I hope we can grow our team onwards as testing will become even more crucial as 
we move forward with the remaining implementation work to reach the minimum 
functionality for multi-attach.

Thank you All once more for the hard work! And see you on the weekly meeting 
next Thursday. :)

Thanks,
Ildikó
(IRC: ildikov)


> On 2017. Dec 9., at 13:15, Matt Riedemann  wrote:
> 
> I just wanted to take a minute to recognize that the patch [1] to make Nova 
> use the new-style Cinder volume attach flow has merged.
> 
> As one can tell from the patch set count alone, this has been in the works 
> for a long time now.
> 
> We were talking about volume multi-attach support back in Mitaka at the 
> midcycle in Bristol. The early talks / patches would have piled more 
> technical debt onto Nova and further baked in Nova's need to manage volume 
> state, which is something we wanted to avoid, so at the Newton summit in 
> Austin we changed course and decided to prioritize working on a new data 
> model and API in Cinder, which eventually came out as the 3.27 volume 
> attachments API in Ocata.
> 
> There was then serious work on both sides in Pike to start using the new 3.27 
> API and we found out we needed some more changes to Cinder, which became the 
> 3.44 Cinder API in Queens. Now Nova has merged the change at the end of a 
> very long series of changes to enable the new flow once 3.44 is available to 
> Nova and computes are all upgraded to understand the new flow. One can 
> appreciate the complexity here if you read through the Nova spec for the new 
> attach flow [2].
> 
> I was really happy to see [1] merge this week because I knew we needed to get 
> that in by the queens-2 milestone if we were going to have a shot at (1) 
> flushing out stability issues before Queens RC1 and (2) a good chance to get 
> multi-attach support into Nova in Queens.
> 
> We have a plan for multi-attach support [3] which I think is doable before 
> feature freeze. The Cinder 3.48 API is now available too which Nova needs to 
> correctly detach a multi-attach volume.
> 
> I want to thank everyone that's helped push this along for their dedication 
> and patience, especially John Griffith, Ildiko Vancsa, Steve Noyes and John 
> Garbutt. And thanks to Sean McGinnis, Jay Bryant, Walter Boring and Balazs 
> Gibizer for review support.
> 
> We've had weekly meetings between the Nova and Cinder teams for at least two 
> years now and I can finally see the end so let's keep up the momentum.
> 
> [1] https://review.openstack.org/#/c/330285/
> [2] 
> https://specs.openstack.org/openstack/nova-specs/specs/queens/approved/cinder-new-attach-apis.html
> [3] 
> https://specs.openstack.org/openstack/nova-specs/specs/queens/approved/cinder-volume-multi-attach.html
> 
> -- 
> 
> 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


__
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] [infra] Retire puppet-apps_site repo

[Andreas Jaeger]

With the retirement of the app-catalog repos and the decommision of
apps.openstack.org, we can retire this repository as well.

I'm proposing a couple of changes with topic:retire-puppet-apps

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
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] The Weekly Owl - 1st Edition

[Or Idgar]

Nice update!
Thanks Emilien!

On Tue, Dec 5, 2017 at 9:48 PM, Emilien Macchi  wrote:

> Note: this is the first edition of a weekly update of what happens in
> TripleO. The goal is to provide a short reading (less than 5 minutes)
> to learn where we are and what we're doing.
> Any contributions or feedback are welcome.
>
>
>
> +--+
> | Continuous Integration |
> +--+
>
> +--> New rover is Sagi and new ruck is Matt. Please let them know any
> new CI issue.
> +--> Team will focus on developers reproduce CI jobs on their own RDO
> Cloud (https://trello.com/c/EWotWxGe)
> +--> Promotions look good so far: Master promoted 12/5/2017 - Pike
> promoted 12/2/2017 - Ocata promoted 12/4/2017
> +--> Newton promotion job now handled by rdo-phase1
> +--> More: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting
>
> +-+
> | Upgrades |
> +-+
>
> +--> Some experimental jobs are WIP to test Fast Forward Upgrades (aka
> FFU). Reviews are needed on https://review.rdoproject.org/r/#/c/10827
> and https://review.openstack.org/#/q/topic:ffu/ci+(status:open+
> OR+status:merged).
> +--> Some work is being done to make upgrade jobs working from Ocata
> to Pike in RDO CI - and in the same time some bugs are being fixed
> regarding this upgrade path.
> +--> tripleo-upgrade upstream repository is being updated from the old
> repo, the team is working on it.
> +--> More: https://etherpad.openstack.org/p/tripleo-upgrade-squad-status
> and https://etherpad.openstack.org/p/tripleo-upgrade-squad-meeting
>
> +---+
> | Containers |
> +---+
>
> +--> k8s: good progress on CI when deploying with Kubespray.
> +--> k8s: working on getting tempest working for ansible-role-k8s-* repos
> +--> k8s: migrated ansible-role-k8s-glance from external github under
> `openstack`
> +--> undercloud: some progress has been made but some bugs are
> currently under investigation (idempotency issues, Registry config,
> etc).
> +--> overcloud: work in progress on image prepare workflows
> +--> overcloud: Paunch now explicitly pulls images before docker run.
> +--> overcloud: we can now have the port in the image name and tag
> discover will still work fine.
> +--> More: https://etherpad.openstack.org/p/tripleo-containers-
> squad-status
>
> +--+
> | Integration |
> +--+
>
> +--> The team is working on Multiple Ceph clusters blueprint and
> Multiple Ceph pools for Cinder.
> +--> The team is preparing the integration to deploy Ceph Luminous!
> +--> Some backports are being done to resolve a CVE:
> https://review.openstack.org/#/q/topic:bug/1720787+(status:
> open+OR+status:merged)
> +--> More: https://etherpad.openstack.org/p/tripleo-integration-
> squad-status
>
> +-+
> | UI/CLI |
> +-+
>
> +--> Roles management ready for review on GUI side, waiting for
> tripleo-common patches to get finished.
> +--> Nodes registration refactoring merged.
> +--> The team is still working on testing Pike.
> +--> Layout changes and refactoring patchset merged
> +--> More: https://etherpad.openstack.org/p/tripleo-ui-cli-squad-status
>
> +---+
> | Validations |
> +---+
> +--> The team has requested more review from TripleO developers,
> please help if you can!
> https://etherpad.openstack.org/p/validations-reviews
> +--> More: https://etherpad.openstack.org/p/tripleo-validations-
> squad-status
>
> +---+
> | Networking |
> +---+
> +--> In the last meeting, the team discussed about the future of
> os-net-config, routed-networks and OVS containerization.
> +--> In the next meeting, the team will discuss about how we can
> prepare nodes for NFV features and the state of  tests for
> containerized deployments and networking.
> +--> Some folks are also focused on Octavia integration.
> +--> More: https://etherpad.openstack.org/p/tripleo-networking-
> squad-status
>
> +--+
> | Workflows |
> +--+
>
> +--> No update this week.
> +--> More: https://etherpad.openstack.org/p/tripleo-workflows-squad-status
>
> ++
> | Weekly Owl |
> ++
>
> The Barn Owl (aka Tyto alba) is a medium sized owl with no ear-tufts
> and a heart-shaped face. These pale, nearly worldwide birds are
> closely associated with man through their traditional use of barn
> lofts and church steeples as nesting sites. The species name "alba"
> refers to the white color. Other names for the Barn Owl have included
> Monkey-faced Owl, Ghost Owl, and Church Owl. (source:
> https://www.owlpages.com/owls/species.php?s=10)
>
>
>
> Stay tuned!
> --
> Your fellow reporter, Emilien Macchi
>
> __
> 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
>