[openstack-dev] [octavia] Please give me some comments about my patchs

[Jeff Yang]

Hi, Octavia Team:
There are two patches I committed:
https://review.openstack.org/#/c/590620/
https://review.openstack.org/#/c/594040/
The first implement l7policy and l7rule's quota management. The second
provides some restrictions about the protocol when listener is associated
with pool.
I think these functions are useful for users. I hope to receive some
suggestions from you.
Thinks.
__
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-Infra] Proposed changes to how we run our meeting

[Jimmy Mcarthur]

Clark Boylan 
November 18, 2018 at 1:09 PM
Hello everyone,

In Berlin there was a forum session on dealing with timezones and 
language barriers. There were a couple related ideas that came out of 
that session. In particular that having meetings only when there is a 
strong agenda helps people avoid staying up all night for nothing and 
that listing an agenda ahead of time can help non english speakers 
better prepare for the meeting.
This is a GREAT idea.  Not just for English speakers, but for everyone. 
I'm a big fan of not having meetings just to fill time.


Both ideas seem sound to me and I think we should try to implement 
them for the Infra team. I propose that we require agenda updates 24 
hours prior to the meeting start time and if there are no agenda 
updates we cancel the meeting. Curious to hear if others think this 
will be helpful and if 24 hours is enough lead time to be helpful.
Love the 24 hour lead time. Looking forward to seeing how this works and 
hope it can be adopted across other projects.


We'll have our meeting this Tuesday (with this item on the agenda), 
but it would probably also be good to use the mailing list for 
feedback as I think that gives us a broader set of potential feedback.


Thanks for taking the lead on this Clark!  Nice work :)


Thank you,
Clark

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [Openstack] (Juno - *sigh*) Want non-admin access to hypervisor:VM association.

[Ken D'Ambrosio]

On 2018-11-18 09:11, Mohammed Naser wrote:

> https://blueprints.launchpad.net/nova/+spec/openstack-api-hostid 
> 
> This should take care of it, don't know if it exists in Juno though.

It *does* exist in Juno, it *can't*, however, do what I want -- at
least, generically.  The hostId that gets returned is a value that's
(apparently) used to let you know, semi-anonymously, how affinity is (or
isn't) working for your VMs.  So you get a unique identifier for each
hypervisor -- but it has no *obvious* bearing on the hostname.   It's an
id that's formed from the SHA224 hash of the ID of your tenant and the
hostname of the hypervisor -- a bit of a catch-22, that, and prevents
you from being able to make use of the hash if you don't know your
back-end.  But... I do.  So I created an associative array with all the
current (and, God willing, future) hypervisor hostnames in my company,
with the key being the hostId/hash, and the value being the hypervisor
name.  Then I queried my VMs, got all the hostIds, used that as the
index to query my associative array, and bingo!  My hypervisor's name. 

Kinda fugly, but when you have a standardized hypervisor hostname
nomenclature, it's sufficient, without having to go mucking about with
changing poorly-documented Nova policy.json stuff in a four-year-old
release of OpenStack. 

I'll take it.  Thanks! 

-Ken 

> On Thu, Nov 15, 2018 at 1:49 PM Ken D'Ambrosio  wrote: 
> 
>> Hey, all.  We've got a Juno cloud, and we'd like various end-users to be 
>> able to see which hypervisors their VMs spring up on.  
>> /etc/nova/policy.json seems to have some relevant info, but it's hard to 
>> tell what does what.   "compute_extension:hypervisors" looks like a 
>> possible candidate, but that's so vague that there's no telling what, 
>> exactly, is meant by "hypervisors".  So:
>> 
>> * Given that I just want the hypervisor:VM association, any suggestions 
>> as to which rule(s) to modify?
>> * Failing that, wondering if there's any for-real documentation on what 
>> the various options in policy.json *do*.  I've found many, many lists of 
>> what's in a generic policy.json, but nothing that went into detail about 
>> what does what.
>> 
>> Thanks!
>> 
>> -Ken
>> 
>> ___
>> 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
> 
> -- 
> Mohammed Naser -- vexxhost
> 
> - 
> D. 514-316-8872 
> D. 800-910-1726 ext. 200 
> E. mna...@vexxhost.com 
> W. http://vexxhost.com [1]

 

Links:
--
[1] http://vexxhost.com/___
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] IMPORTANT: We're combining the lists!

[Jeremy Stanley]

REMINDER: The openstack, openstack-dev, openstack-sigs and
openstack-operators mailing lists (to which this was sent) are being
replaced by a new openstack-disc...@lists.openstack.org mailing
list. The new list[0] is open for posts from subscribers starting
now, and the old lists will be configured to no longer accept posts
starting on Monday December 3. In the interim, posts to the old
lists will also get copied to the new list so it's safe to
unsubscribe from them now and not miss any messages. See my previous
notice[1] for details.

As of the time of this announcement, we have 280 subscribers on
openstack-discuss with three weeks to go before the old lists are
closed down for good). At the recommendation of David Medberry at
the OpenStack Summit last week, this reminder is being sent
individually to each of the old lists (not as a cross-post), and
without any topic tag in case either might be resulting in
subscribers missing it.

[0] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1] 
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
-- 
Jeremy Stanley


signature.asc
Description: PGP signature
___
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] IMPORTANT: We're combining the lists!

[Jeremy Stanley]

REMINDER: The openstack, openstack-dev, openstack-sigs and
openstack-operators mailing lists (to which this was sent) are being
replaced by a new openstack-disc...@lists.openstack.org mailing
list. The new list[0] is open for posts from subscribers starting
now, and the old lists will be configured to no longer accept posts
starting on Monday December 3. In the interim, posts to the old
lists will also get copied to the new list so it's safe to
unsubscribe from them now and not miss any messages. See my previous
notice[1] for details.

As of the time of this announcement, we have 280 subscribers on
openstack-discuss with three weeks to go before the old lists are
closed down for good). At the recommendation of David Medberry at
the OpenStack Summit last week, this reminder is being sent
individually to each of the old lists (not as a cross-post), and
without any topic tag in case either might be resulting in
subscribers missing it.

[0] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1] 
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
-- 
Jeremy Stanley


signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[openstack-dev] IMPORTANT: We're combining the lists!

[Jeremy Stanley]

REMINDER: The openstack, openstack-dev, openstack-sigs and
openstack-operators mailing lists (to which this was sent) are being
replaced by a new openstack-disc...@lists.openstack.org mailing
list. The new list[0] is open for posts from subscribers starting
now, and the old lists will be configured to no longer accept posts
starting on Monday December 3. In the interim, posts to the old
lists will also get copied to the new list so it's safe to
unsubscribe from them now and not miss any messages. See my previous
notice[1] for details.

As of the time of this announcement, we have 280 subscribers on
openstack-discuss with three weeks to go before the old lists are
closed down for good). At the recommendation of David Medberry at
the OpenStack Summit last week, this reminder is being sent
individually to each of the old lists (not as a cross-post), and
without any topic tag in case either might be resulting in
subscribers missing it.

[0] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1] 
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
-- 
Jeremy Stanley


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-Infra] Proposed changes to how we run our meeting

[Melvin Hillsman]

++

On Sun, Nov 18, 2018 at 2:32 PM Jeremy Stanley  wrote:

> On 2018-11-18 11:09:29 -0800 (-0800), Clark Boylan wrote:
> [...]
> > I propose that we require agenda updates 24 hours prior to the
> > meeting start time and if there are no agenda updates we cancel
> > the meeting. Curious to hear if others think this will be helpful
> > and if 24 hours is enough lead time to be helpful.
> [...]
>
> Sounds great to me, thanks for considering putting these ideas into
> practice!
> --
> Jeremy Stanley
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra



-- 
Kind regards,

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

Re: [OpenStack-Infra] Proposed changes to how we run our meeting

[Jeremy Stanley]

On 2018-11-18 11:09:29 -0800 (-0800), Clark Boylan wrote:
[...]
> I propose that we require agenda updates 24 hours prior to the
> meeting start time and if there are no agenda updates we cancel
> the meeting. Curious to hear if others think this will be helpful
> and if 24 hours is enough lead time to be helpful.
[...]

Sounds great to me, thanks for considering putting these ideas into
practice!
-- 
Jeremy Stanley


signature.asc
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Proposed changes to how we run our meeting

[Clark Boylan]

Hello everyone,

In Berlin there was a forum session on dealing with timezones and language 
barriers. There were a couple related ideas that came out of that session. In 
particular that having meetings only when there is a strong agenda helps people 
avoid staying up all night for nothing and that listing an agenda ahead of time 
can help non english speakers better prepare for the meeting.

Both ideas seem sound to me and I think we should try to implement them for the 
Infra team. I propose that we require agenda updates 24 hours prior to the 
meeting start time and if there are no agenda updates we cancel the meeting. 
Curious to hear if others think this will be helpful and if 24 hours is enough 
lead time to be helpful.

We'll have our meeting this Tuesday (with this item on the agenda), but it 
would probably also be good to use the mailing list for feedback as I think 
that gives us a broader set of potential feedback.

Thank you,
Clark

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Sysadmin

[Clark Boylan]

On Sat, Nov 17, 2018, at 9:34 AM, Mathias Gutehall wrote:
> Hi all,
> 
> I just wanted to check if there’s any need for a sysadmin with long 
> experience with Unix/Linux systems in this project? I’m based in Sweden 
> and have been working as a sysadmin since 1995 and since the 3 years 
> with cloud services.

We are always happy to have more help running the community developer 
infrastructure. A good place to start is probably with this document, 
https://docs.openstack.org/infra/system-config/project.html, as it gives a high 
level overview of how we operate and are organized.

To summarize here quickly, we are a community effort to build and run developer 
tooling. We use code review and automated deployment tooling which allows 
people to contribute without having root. If you'd like to get involved and 
become a root the process for that is to start through the code review system 
and take advantage of our automated deployments.

I like to encourage individuals find a task that interests them and start from 
there. Some of the big efforts we currently have are:

1. Modernize configuration management
1a. Convert to ansible for configuration management (gerrit 
topic:update-cfg-mgmt)
1b. Update puppet 3 to puppet 4 since the ansible conversion won't happen 
immediately (gerrit topic:puppet-4)
1c. Use docker images and containers to deploy software, particularly that 
which we install from source
2. IRC bot update to handle the large number of channels we talk to with common 
tooling
3. Gerrit upgrade to 2.15 (may be related to 1a and 1c)
4. OpenDev transition, though this is new and doesn't have many concrete 
actions yet.

There are other items as well. Feel free to follow up with this list, myself or 
on IRC if any of this does interest you and we can go from there.

Hope this helps,
Clark

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [Openstack] (Juno - *sigh*) Want non-admin access to hypervisor:VM association.

[Mohammed Naser]

https://blueprints.launchpad.net/nova/+spec/openstack-api-hostid

This should take care of it, don't know if it exists in Juno though.

On Thu, Nov 15, 2018 at 1:49 PM Ken D'Ambrosio  wrote:

> Hey, all.  We've got a Juno cloud, and we'd like various end-users to be
> able to see which hypervisors their VMs spring up on.
> /etc/nova/policy.json seems to have some relevant info, but it's hard to
> tell what does what.   "compute_extension:hypervisors" looks like a
> possible candidate, but that's so vague that there's no telling what,
> exactly, is meant by "hypervisors".  So:
>
> * Given that I just want the hypervisor:VM association, any suggestions
> as to which rule(s) to modify?
> * Failing that, wondering if there's any for-real documentation on what
> the various options in policy.json *do*.  I've found many, many lists of
> what's in a generic policy.json, but nothing that went into detail about
> what does what.
>
> Thanks!
>
> -Ken
>
> ___
> 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
>


-- 
Mohammed Naser — vexxhost
-
D. 514-316-8872
D. 800-910-1726 ext. 200
E. mna...@vexxhost.com
W. http://vexxhost.com
___
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

Re: [openstack-dev] [nova] Can we deprecate the server backup API please?

[Alex Xu]

Sounds make sense to me, and then we needn't fix this strange behaviour
also https://review.openstack.org/#/c/409644/

Jay Pipes  于2018年11月17日周六 上午3:56写道：

> The server backup API was added 8 years ago. It has Nova basically
> implementing a poor-man's cron for some unknown reason (probably because
> the original RAX Cloud Servers API had some similar or identical
> functionality, who knows...).
>
> Can we deprecate this functionality please? It's confusing for end users
> to have an `openstack server image create` and `openstack server backup
> create` command where the latter does virtually the same thing as the
> former only sets up some whacky cron-like thing and deletes images after
> some number of rotations.
>
> If a cloud provider wants to offer some backup thing as a service, they
> could implement this functionality separately IMHO, store the user's
> requested cronjob state in their own system (or in glance which is kind
> of how the existing Nova createBackup functionality works), and run a
> simple cronjob executor that ran `openstack server image create` and
> `openstack image delete` as needed.
>
> This is a perfect example of an API that should never have been added to
> the Compute API, in my opinion, and removing it would be a step in the
> right direction if we're going to get serious about cleaning the Compute
> API up.
>
> Thoughts?
> -jay
>
> __
> 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