Re: [openstack-dev] [horizon][keystone]

[Lin Hua Cheng]

Hi David,

Sounds good.

I am able to download both files, thanks!

Regards,
Lin

On Sat, Nov 14, 2015 at 4:04 AM, David Chadwick 
wrote:

> Hi Lin
>
> I am submitting the code and dissertation links to the mailing list so
> that I only need to do it once for everyone.
>
> Since these are large files, I have sent them to Dropbox. They are
> public access, available as follows:
>
> Brida_Final Dissertation.pdf (3.5Mb)
> (
> https://www.dropbox.com/s/ugyrffgjkmq1a3s/Brinda_Final%20Dissertation.pdf?dl=0
> )
>
> and
>
> Corpus.zip  (12.7Mb)
> (https://www.dropbox.com/s/98fp2c9194n198j/corpus.zip?dl=0)
>
> regards
>
> David
>
> On 14/11/2015 02:59, Lin Hua Cheng wrote:
> > David,
> >
> > FYI, I've submitted a patch to enable registering Identity Providers in
> > horizon:
> >
> > https://review.openstack.org/#/c/244991/
> >
> > The next logical step for this is to look at the IdP mapping.
> >
> > I can follow-up on the work by Anton to add that support for horizon.
> >
> > Can you send me the code and documents you may have related to this?
> >
> > Thanks,
> > Lin
> >
> >
> >
> > On Wed, Oct 7, 2015 at 11:12 AM, David Chadwick  > > wrote:
> >
> >
> >
> > On 07/10/2015 18:29, Adam Young wrote:
> > > On 10/07/2015 11:51 AM, Adam Young wrote:
> > >> Send me what you have, and I will post it as a Work in progress
> review
> > >> against Horizon.  That way at least it will be available for
> others to
> > >> look at and potentially adopt.
> > >
> > > Review has been posted here
> > > https://review.openstack.org/232114
> > >
> >
> > thanks Adam
> >
> > >
> > > I made a best guess as far as where it it should be placed in the
> source
> > > tree.  I have not tested the code.
> > >
> > > David and I have both signed the CLA. I am fairly certon Anton did
> not.
> > > It would be easiest for OpenStack to accept this code if he did, as
> > > there would be no question about copyright or licensing.
> >
> > Legally speaking it is not necessary, since any code produced by
> > students as part of their degree course does not belong to them.
> > However, it would be courteous of us to ask him, so I have done this.
> >
> > >
> > > David also provided me with a PDF version of Anton's dissertation.
> I do
> > > not know what the status of that document, but it would be a great
> > > resource to anyone that wants to take this code and get it
> integrated
> > > into Horizon.
> >
> > This can be made publicly available after the exam board next month.
> > Until then I will give out personal copies for private study.
> >
> > regards
> >
> > David
> >
> > >
> > > This does not look like a radical stretch.  It would be a decent
> > > opportunity for anyone looking to get involved with OpenStack to
> step
> > > into something immediately.
> > >
> > >
> > >
> > >
> > >>
> > >>
> > >>
> > >> On 10/07/2015 11:37 AM, David Chadwick wrote:
> > >>> Hi Douglas
> > >>>
> > >>> we are happy for you (or someone else) to submit the code in 3
> > names:
> > >>> theirs, mine and Anton's. Then this third person can do all the
> work
> > >>> necessary to get it approved. In this way it is legitimate,
> > since the
> > >>> third person will have contributed to the overall effort.
> > >>>
> > >>> I dont have any spare time yet for another month or so. After
> that I
> > >>> could submit it, but having never done it before for Horizon,
> > there will
> > >>> be a big learning curve. And I might not have time to learn it
> > >>>
> > >>> regards
> > >>>
> > >>> David
> > >>>
> > >>> On 07/10/2015 16:05, Douglas Fish wrote:
> >  Hi David,
> >    This sounds like a great set of code, I'm sure we are going to
> >  realize
> >  we want it sooner or later! Unfortunately I can't consume code
> > in this
> >  way (I can't propose code written by somebody else) and I can't
> > spend
> >  significant time on it right now.
> >    Would you or Anton be willing to propose whatever code and
> >  documentation
> >  you have to Horizon? It doesn't have to be complete; it doesn't
> > need to
> >  have grammar cleaned up or anything like that. You could mark
> > it as a
> >  "Work in progress", and make it clear in the commit message
> > that you
> >  aren't planning further work on this, so the patch is available
> for
> >  adoption. That way somebody else may be able to pick this up and
> >  work on
> >  it in the future, but Anton could get credit for the work he
> > has done.
> > 
> >  Doug Fish
> > 
> >   - Original message -
> >   From: David Chadwick  > >
> > 

[openstack-dev] [nova] [nova-compute-node] [installation]

[Ernesto Valentino]

Hi everyone,
I've just finished the installation of a nova compute node (juno) following
each instruction of the documentation of OS.
The service is (nova service-list figure out that my pc is in the list) but
when i try to instantiate a new vm i got this stuck on the build status
(scheduling task). From my nova-compute.log i see that when i instantiate
the vm i get this error:

2015-11-14 21:29:49.063 28137 ERROR object
[req-3dae22c0-f65f-4a3d-903e-835ee7ea4185 3f6b0a08e0d74d5f82c240d8a7860404
26cc6b29f6b24c5ebff8131f306602cc] Unable to instantiate unregistered object
type NetworkRequestList

If someone could help me i really appreciate because i got no idea of where
the problem is. Thanks so much for answering.

Best regards,
Ernesto
__
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] [openstack-infra] python-vitrageclient project acl config

[Andreas Jaeger]

On 11/14/2015 05:49 PM, GROSZ, Maty (Maty) wrote:

Hello... I have pusged a change,
https://review.openstack.org/#/c/245433/.I was expecting, based on the
project configuration, that vitrage-core gerrit group with have
permission to review and set +2
Now, I am also included in the vitrage-core, but when I want to add a
comecnt in gerrit - I don't have the option to set + 2 as I was
expected. What is wrong?


The ACLs did not get setup, I've started already a separate thread on 
openstack-infra about this,


Andreas
--
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: 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

[openstack-dev] [kolla] Rollcall vote on kolla-mesos spec

[Steven Dake (stdake)]

From: Steven Dake mailto:std...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Saturday, November 14, 2015 at 10:59 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] Rollcall vote on kolla-mesos spec needs one more vote

https://review.openstack.org/#/c/241086/

This spec has had plenty of time for the Kolla core reviewers to review the 
spec.  A rollcall vote is a majority vote with no veto power.  The reason there 
is no veto power is because if the majority wants to proceed, one angry soul 
shouldn't stop progress :)

Please if you haven't had a chance to review the spec have a review, and if you 
like it, since we have 9 core reviewers at the moment, feel free to +A the spec 
as well.

Regards
-steve

__
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] [kolla] Action needed on blueprint development

[Steven Dake (stdake)]

Well folks

Now that we have all finally recovered from Summit and I spent awhile creating 
blueprints for Mitaka based upon our design summit sessions.  Our plans as 
discussed at summit were to release a 1.1.0 version which is semi-forward 
compatible from 1.0.1.  From that point forward all upgrades of Kolla will work 
without a hitch.  We think 1.0.1 is not ideal to deploy at the moment because 
certain things may not work during an upgrade in the future (ovs database for 
one would be lost).

1.1.0 is our collective attempt to prepare Kolla to be upgradeable from Mitaka 
to N and also allow continuous deployment of the OpenStack specific services 
throughout the Mitaka cycle if people are brave enough for that.

Please pitch in and take a blueprint here::

https://launchpad.net/kolla/+milestone/mitaka-1

The deadline for Mitaka 1 is December 4th.  The blueprints I speak of for this 
1.1.0 release are all marked as "Essential" as they will be backported into 
stable/liberty.

Thanks for your help!

Regards,
-steve


__
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] Rollcall vote on kolla-mesos spec needs one more vote

[Steven Dake (stdake)]

https://review.openstack.org/#/c/241086/

This spec has had plenty of time for the Kolla core reviewers to review the 
spec.  A rollcall vote is a majority vote with no veto power.  The reason there 
is no veto power is because if the majority wants to proceed, one angry soul 
shouldn't stop progress :)

Please if you haven't had a chance to review the spec have a review, and if you 
like it, since we have 9 core reviewers at the moment, feel free to +A the spec 
as well.

Regards
-steve

__
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] [stable] Call for testing: 2014.2.4 candidate tarballs

[Alan Pevec]

Hi all,

we are scheduled to publish 2014.2.4, last Juno point release,
on Thursday November 19th for Ceilometer, Cinder, Glance, Heat,
Horizon, Keystone, Neutron, Nova, Sahara and Trove.
Draft release notes are available at
https://wiki.openstack.org/wiki/ReleaseNotes/2014.2.4

We'd appreciate anyone who could test the candidate 2014.2.4 tarballs:

  http://tarballs.openstack.org/ceilometer/ceilometer-stable-juno.tar.gz
  http://tarballs.openstack.org/cinder/cinder-stable-juno.tar.gz
  http://tarballs.openstack.org/glance/glance-stable-juno.tar.gz
  http://tarballs.openstack.org/heat/heat-stable-juno.tar.gz
  http://tarballs.openstack.org/horizon/horizon-stable-juno.tar.gz
  http://tarballs.openstack.org/keystone/keystone-stable-juno.tar.gz
  http://tarballs.openstack.org/neutron/neutron-stable-juno.tar.gz
  http://tarballs.openstack.org/nova/nova-stable-juno.tar.gz
  http://tarballs.openstack.org/sahara/sahara-stable-juno.tar.gz
  http://tarballs.openstack.org/trove/trove-stable-juno.tar.gz


Thanks,
Alan

__
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-infra] python-vitrageclient project acl config

[GROSZ, Maty (Maty)]

Hello... I have pusged a change, https://review.openstack.org/#/c/245433/. I 
was expecting, based on the project configuration, that vitrage-core gerrit 
group with have permission to review and set +2
Now, I am also included in the vitrage-core, but when I want to add a comecnt 
in gerrit - I don't have the option to set + 2 as I was expected. What is wrong?


Maty Grosz
DevOps Group Lead
Alcatel-Lucent
CloudBand Business Unit
16 Atir Yeda St. Kfar-Saba 44643, ISRAEL
T:  +972 (0) 9 793 3078
maty.gr...@alcatel-lucent.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

Re: [openstack-dev] [horizon][keystone]

[David Chadwick]

Hi Lin

I am submitting the code and dissertation links to the mailing list so
that I only need to do it once for everyone.

Since these are large files, I have sent them to Dropbox. They are
public access, available as follows:

Brida_Final Dissertation.pdf (3.5Mb)
(https://www.dropbox.com/s/ugyrffgjkmq1a3s/Brinda_Final%20Dissertation.pdf?dl=0)

and

Corpus.zip  (12.7Mb)
(https://www.dropbox.com/s/98fp2c9194n198j/corpus.zip?dl=0)

regards

David

On 14/11/2015 02:59, Lin Hua Cheng wrote:
> David, 
> 
> FYI, I've submitted a patch to enable registering Identity Providers in
> horizon:
> 
> https://review.openstack.org/#/c/244991/
> 
> The next logical step for this is to look at the IdP mapping.
> 
> I can follow-up on the work by Anton to add that support for horizon. 
> 
> Can you send me the code and documents you may have related to this?
> 
> Thanks,
> Lin
> 
> 
> 
> On Wed, Oct 7, 2015 at 11:12 AM, David Chadwick  > wrote:
> 
> 
> 
> On 07/10/2015 18:29, Adam Young wrote:
> > On 10/07/2015 11:51 AM, Adam Young wrote:
> >> Send me what you have, and I will post it as a Work in progress review
> >> against Horizon.  That way at least it will be available for others to
> >> look at and potentially adopt.
> >
> > Review has been posted here
> > https://review.openstack.org/232114
> >
> 
> thanks Adam
> 
> >
> > I made a best guess as far as where it it should be placed in the source
> > tree.  I have not tested the code.
> >
> > David and I have both signed the CLA. I am fairly certon Anton did not.
> > It would be easiest for OpenStack to accept this code if he did, as
> > there would be no question about copyright or licensing.
> 
> Legally speaking it is not necessary, since any code produced by
> students as part of their degree course does not belong to them.
> However, it would be courteous of us to ask him, so I have done this.
> 
> >
> > David also provided me with a PDF version of Anton's dissertation. I do
> > not know what the status of that document, but it would be a great
> > resource to anyone that wants to take this code and get it integrated
> > into Horizon.
> 
> This can be made publicly available after the exam board next month.
> Until then I will give out personal copies for private study.
> 
> regards
> 
> David
> 
> >
> > This does not look like a radical stretch.  It would be a decent
> > opportunity for anyone looking to get involved with OpenStack to step
> > into something immediately.
> >
> >
> >
> >
> >>
> >>
> >>
> >> On 10/07/2015 11:37 AM, David Chadwick wrote:
> >>> Hi Douglas
> >>>
> >>> we are happy for you (or someone else) to submit the code in 3
> names:
> >>> theirs, mine and Anton's. Then this third person can do all the work
> >>> necessary to get it approved. In this way it is legitimate,
> since the
> >>> third person will have contributed to the overall effort.
> >>>
> >>> I dont have any spare time yet for another month or so. After that I
> >>> could submit it, but having never done it before for Horizon,
> there will
> >>> be a big learning curve. And I might not have time to learn it
> >>>
> >>> regards
> >>>
> >>> David
> >>>
> >>> On 07/10/2015 16:05, Douglas Fish wrote:
>  Hi David,
>    This sounds like a great set of code, I'm sure we are going to
>  realize
>  we want it sooner or later! Unfortunately I can't consume code
> in this
>  way (I can't propose code written by somebody else) and I can't
> spend
>  significant time on it right now.
>    Would you or Anton be willing to propose whatever code and
>  documentation
>  you have to Horizon? It doesn't have to be complete; it doesn't
> need to
>  have grammar cleaned up or anything like that. You could mark
> it as a
>  "Work in progress", and make it clear in the commit message
> that you
>  aren't planning further work on this, so the patch is available for
>  adoption. That way somebody else may be able to pick this up and
>  work on
>  it in the future, but Anton could get credit for the work he
> has done.
> 
>  Doug Fish
> 
>   - Original message -
>   From: David Chadwick  >
>   To: OpenStack Development Mailing List
>    >
>   Cc:
>   Subject: [openstack-dev] [horizon][keystone]
>   Date: Tue, Oct 6, 2015 2:13 PM
> Dear All
> 
>   One of my students, Anton Brida, has developed an Attribute
>  Mapping GUI
>   for Horizon as part 

[openstack-dev] [All] Use of self signed certs in endpoints

[Xav Paice]

Hi,

I'm sure I'm not the only one that likes to use SSL everywhere possible,
and doesn't like to pay for 'real' ssl certs for dev environments.
Figuring out how to get requests to allow connection to the self signed
cert would have paid for a real cert many times over.

When I use an SSL cert with a CA not in the Mozilla bundle, and use
keystonemiddleware to access Keystone endpoints, the ssl verification
rightly fails.  It turns out requests doesn't use the system ca cert
bundle, but has it's own.  It's also got a nice easy config option to set
which ca cert bundle you want to use -
http://docs.python-requests.org/en/latest/user/advanced/?highlight=ca_bundle#ssl-cert-verification

How do people feel about having that as a config option set somewhere, so
we can specify a ca cert in, say, heat.conf, so that we can continue with
the self signed certs of cheapness without needing to hack up the
cacert.pem that comes with requests, or find a way to pass in environment
variables?

Am I barking up the wrong tree here?  How would I go about writing a
blueprint for this, and for which project?  I guess it's something that
would need to be added to all the projects in the keystone_authtoken
section?  Or is there a central place where common configs like this can
live?
__
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