Hi All,
I will be helping to moderating the Quotas and Billing session, or as
I like to call it, Billing and Quotas. ;)
The etherpad is here:
https://etherpad.openstack.org/p/TYO-ops-quotas-and-billing
Schedule entry: http://sched.co/4Nkg
If you are interested in these subjects please do fill o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hey everyone!
Thanks to Tom and believing in our project he's given us a room[1] to
get some work done. I've started a etherpad here[2] to start putting
down some thoughts.
This is great news, please put any topics or thoughts so we can make
sure
Hi all,
No Telco Working Group meeting Wednesday October 20th due to proximity to the
F2F in Tokyo and the lack of items to discuss. See you all next Tuesday!
Thanks,
Steve
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
- Original Message -
> From: "Steve Gordon"
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
>
> Hi all,
>
> No Telco Working Group meeting Wednesday October 20th due to proximity to the
Obviously I meant 21st, apologies!
-Steve
> F2F in Tokyo and the lack of
I’ve gone ahead and (somewhat arbitrarily) scheduled out the lightning talks
between the sessions on Tuesday and Wednesday:
https://etherpad.openstack.org/p/TYO-ops-lightning-talks
Please confirm your timeslot, or if you need to go on the opposite day, update
the etherpad.
A few talks have bee
Could we get the etherpad link added to the sched page for this please?
On 10/20/15, 11:16 AM, "JJ Asghar" wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA512
>
>
>Hey everyone!
>
>Thanks to Tom and believing in our project he's given us a room[1] to
>get some work done. I've started a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/20/15 3:08 PM, Mike Dorman wrote:
> Could we get the etherpad link added to the sched page for this please?
Great idea, I've CC'd Tom on this, I don't think i have access to make
this happen.
Tom, the etherpad is: https://etherpad.openstack.o
Done :)
Would you like to add any further description about the project / team and who
should attend in sched, for those who may not be familiar?
> On Oct 20, 2015, at 3:20 PM, JJ Asghar wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 10/20/15 3:08 PM, Mike Dorman wrote:
Hello,
I am trying to use a module to automate VM deployments. I can't connect to
keystone externally so it will make new tenants. What is the best route to
allow access?
I am using kilo.
Sent from my iPhone
___
OpenStack-operators mailing list
Ope
You should have your public endpoints be externally reachable.
> On Oct 20, 2015, at 2:38 PM, Sesso wrote:
>
> Hello,
>
> I am trying to use a module to automate VM deployments. I can't connect to
> keystone externally so it will make new tenants. What is the best route to
> allow access?
> I
I have this below.
publicurl |
internalurl| adminurl
https://public.domain.com:5000/v2.0 | http://192.168.0.2:5000/v2.0
| http://192.168.0.2:35357/v2
Great Idea Lauren as all these things are blurring together in my mind.
On Tue, Oct 20, 2015 at 2:47 PM, Lauren Sell wrote:
> Done :)
>
> Would you like to add any further description about the project / team and
> who should attend in sched, for those who may not be familiar?
>
>
> > On Oct 20
Hi Jason,
Certain commands can only be executed via admin url, which in your case may not
be routable from external networks. You would need to consider changing the
admin endpoint to an ip/FQDN that can be accessed externally (like public url)
or limit the ability to execute those particular c
One simple workaround for this if you ssh directly to your Keystone node
and run the admin commands from there. Once you bootstrap your project with
the proper tenants and users it's not an operation that most people do all
that often. We expose an admin endpoint on an internal load balancer URL
bu
how difficult is it to change the admin endpoint to a public url?
> On Oct 20, 2015, at 5:28 PM, Matt Fischer wrote:
>
> One simple workaround for this if you ssh directly to your Keystone node and
> run the admin commands from there. Once you bootstrap your project with the
> proper tenants a
It's simple. Just delete the existing one, keystone endpoint-delete
and then re-create it. However you should follow James's advice and make
sure you understand the security implications first.
On Tue, Oct 20, 2015 at 7:21 PM, Sesso wrote:
> how difficult is it to change the admin endpoint to a
16 matches
Mail list logo
