Hi Sean/Morgan,
I think there is room for the proper use of keystoneauth sessions in the
Keystone v3 only cross-project session too:
https://etherpad.openstack.org/p/newton-keystone-v3-devstack
Feel free to add anything related to ksa sessions.
Henrique
Em seg, 18 de abr de 2016 às 11:06, Morga
Hi Sean,
I don't think they're supposed to work with that. Both of those clients
have their python API compatible with those variables you've commented. But
the CLI should be used through OpenStack client. Just for an example,
keystoneclient CLI does not support it, but OpenStack client supports
k
Hi Sean,
I've been working on v3 only related stuff in a while and I volunteer on
this too.
Henrique
Em ter, 2 de fev de 2016 às 05:41, Julien Danjou
escreveu:
> On Mon, Feb 01 2016, Sean Dague wrote:
>
> > The revert is here - https://review.openstack.org/#/c/274703/ - and will
> > move it's
Hi, Did exporting the variables solve your problem? I'm working on
improving the support of v3 in devstack, like the openrc you've mentioned.
Em qui, 14 de jan de 2016 às 06:50, Akihiro Motoki
escreveu:
> devstack creates /etc/openstack/clouds.yaml (os-client-config
> configuraiton files) which
I'm in! And hope I can put some other folks in too.
Em sáb, 10 de out de 2015 às 12:03, Lance Bragstad
escreveu:
> On Sat, Oct 10, 2015 at 8:07 AM, Boris Bobrov
> wrote:
>
>> On Saturday 10 October 2015 08:42:10 Shinobu Kinjo wrote:
>> > So what's the procedure?
>>
>> You go to #openstack-keyst
Hi Folks,
As you may know, the Reseller Blueprint was proposed and approved in Kilo (
https://review.openstack.org/#/c/139824/) with the developing postponed to
Liberty.
During this time, the 3 main patches of the chain were split into 8,
becoming smaller and easier to review. The first 2 of them
I mean project names. You can, for example, create a project today with a
name like "dev/tests".
Em seg, 6 de jul de 2015 às 03:56, Sam Morrison
escreveu:
> Do you mean project names or project IDs?
>
> Sam
>
>
> On 3 Jul 2015, at 12:12 am, Henrique Truta
> wrot
Hi everyone,
In Kilo, keystone introduced the concept of Hierarchical Multitenancy[1],
which allows cloud operators to organize projects in hierarchies. This
concept is evolving in Liberty, with the addition of the Reseller use
case[2], where among other features, it’ll have hierarchies of domains
Hi all,
We are proposing a spec[1], on which we describe how the deletion and
disablement of a subtree will work. This change improves the usabilty of
Reseller/Hierarchical Multitenancy that are two of the biggest Keystone
additions in the last releases. This feature will make it easier for
operat
gt; > expect with implementing option #2 (which at face value feels to be API
> > incompatible/break of current behavior).
> >
> > Cheers,
> > --Morgan
> >
> > On Tue, Jun 2, 2015 at 7:43 AM, Henrique Truta
> > mailto:henriquecostatr...@gmail.com>>
Hi folks,
In Reseller[1], we’ll have the domains concept merged into projects, that
means that we will have projects that will behave as domains. Therefore, it
will be possible to have two projects with the same name in a hierarchy,
one being a domain and another being a regular project. For insta
Hi Tim,
Maybe you should consider Monasca[1], Monitoring At Scale solution for
OpenStack, or, at least, a few concepts of it.
[1] https://wiki.openstack.org/wiki/Monasca
[]s
Henrique Truta
Em ter, 26 de mai de 2015 às 14:49, Tim Bell escreveu:
>
>
> We had a good discussion at t
Hi Abhishek,
You can change it directly using KVM/Qemu command line. However, nova
probably won't be notified and the information on the database will be
outdated.
Em ter, 7 de abr de 2015 às 06:04, Abhishek Talwar/HYD/TCS <
abhishek.tal...@tcs.com> escreveu:
> Hi Folks,
>
> When we boot an inst
and the
latter considers on adding a "change rate" comparator, which will enable
to set the growth rate as the threshold.
What do you think about it?
Best Regards
--
Henrique Truta
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstac
gt;
> Somewhere on my large TODO is to get this info back into the devstack
> README (it used to be there).
>
> -Sean
>
> On 05/20/2014 10:15 AM, Henrique Truta wrote:
> > Hello, Sean!
> >
> > I'm trying to use Nova Network instead of Neutron due to i
a Host... I'll try to
disable the Cinder API.
The most strange part is that I run stack.sh on the compute node, and ir
runs ok, but it doesn't create anything. Appearantly, it only uses the API
on the Controller :/
2014-05-19 18:10 GMT-03:00 Collins, Sean :
> On Mon, May 19, 2
Yes, I am.
Controller localrc: http://paste.openstack.org/show/80953/
Compute node localrc: http://paste.openstack.org/show/80955/
2014-05-19 17:51 GMT-03:00 Collins, Sean :
> On Mon, May 19, 2014 at 04:44:05PM EDT, Henrique Truta wrote:
> > Hello, everyone!
> >
> >
ost-list" and I only get the
the controller host.
I've folowed all the steps described on the guide (
http://devstack.org/guides/multinode-lab.html) and it worked on Ubuntu
Server, but not on CentOS.
Can anyone help me?
Thanks!
--
--
Henrique Truta
at where the controller should be
> implemented?
>
> We regard implementing the controller in nova scheduler as the first
> choice. And we also consider extending ceilometer.(Ie. When ceilometer
> discovers an overload host, an alarm can be reported and it can trigger a
> vm evacuat
Hello!
I'm currently investigating both of these features you have mentioned,
specifically on the NEAT[1] and GANTT[2] projects, as you might see on the
last week discussion.
Do you have any further ideas about how and why this would work with Heat?
Thanks,
Henrique
[1] http://openstack-neat.o
;>>> [1]
>>>>> http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=
>>>>> AN&subtype=CA&htmlfid=897/ENUS213-590&appname=USN
>>>>> [2]
>>>>> https://blueprints.launchpad.net/nova/+spec/resource-
>>>>>
@Oleg, @Sylvain, @Leandro, Thanls. I'll check the Gantt project and the
blueprint
2014-04-09 12:59 GMT-03:00 Sylvain Bauza :
>
>
>
> 2014-04-09 17:47 GMT+02:00 Jay Lau :
>
> @Oleg, Till now, I'm not sure the target of Gantt, is it for initial
>> placement policy or run time policy or both, can y
Hello, everyone!
I am currently a graduate student and member of a group of contributors to
OpenStack. We believe that a dynamic scheduler could improve the efficiency
of an OpenStack cloud, either by rebalancing nodes to maximize performance
or to minimize the number of active hosts, in order to
Hi all!
I've been working on a prototype of Domains in Nova. In that prototype the
user is now able to do the following API calls with a domain scoped token:
GET v2/domains/{domain_id}/servers: Lists servers which projects belong to
the given domain
GET v2/domains/{domain_id}/servers/{server_id}:
formations, which will be included as mentioned in item 3. Then, the Nova
API calls will be changed to consider the domain information and when a
call referent to a project is made (e.g. servers).
What do you think about it? Any additional suggestions?
Thanks.
Henr
25 matches
Mail list logo
