On 2016-06-08 23:08:16 +1000 (+1000), Joshua Hesketh wrote:
> On Mon, Jun 6, 2016 at 9:21 AM, Jeremy Stanley wrote:
> [...]
> > Store Build Logs in Swift
> [...]
> > We should remove the original spec from our priority list (since
> > that's basically already cease
cale static.o.o horizontally.
Yes, and it's not the only lengthy static.o.o outage we've had over
the past month either. I agree that solving it is a good candidate
for prioritization, but we need to go back and choose between a
couple of options on the table
esources and grow slowly, from the more resource-hungry storage sites
> (logs.o.o, tarballs.o.o...).
Agreed, that's actually a pretty trivial change, comparatively
speaking.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra
On 2016-06-21 17:34:07 + (+), Jeremy Stanley wrote:
> On 2016-06-21 18:16:49 +0200 (+0200), Thierry Carrez wrote:
> > It hurts a lot when it's down because of so many services being served from
> > it. We could also separate the published websites (status.o.o
er than self-owned
(because you don't want CI operators adding voting rights for other
CI operators).
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
t::mirror_update class fire every 2
hours currently.
http://git.openstack.org/cgit/openstack-infra/system-config/tree/modules/openstack_project/manifests/mirror_update.pp
>
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists
ove accounts from it without being a member of thatt
group themselves.
https://review.openstack.org/#/admin/groups/1487,info
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
ile at all...
http://git.openstack.org/cgit/openstack/group-based-policy/tree/tox.ini?h=stable%2Fliberty
You probably want to try cherry-picking a backport of
https://review.openstack.org/298959 to that branch.
--
Jeremy Stanley
___
OpenStack-Infra mail
en one along with some means to find out that
redeployment is failing so that it can effectively be troubleshot
post-mortem.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mail
update a persistent haproxy pool. Proxying rather than
redirecting probably makes the most sense as we can avoid presenting
IP-address-based URLs to the consumer (and if we're forced to deploy
with TLS then we might be able to stabilize a solution for that at
the proxy too).
--
Jeremy Stanley
___
han using a
Web browser to make DNS changes through their similarly proprietary
dashboard site.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
lace with fresh servers
each time and bootstrap DevStack from scratch, though perhaps that's
overkill?
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
ntervention to correct.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Thursday (August 4). Unless there are serious
objections by then, I'll go ahead and approve it.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
t;Neil Jerram
(neil-jerram)" but you need that to be an LP group instead with
the "OpenStack Infra (hudson-openstack)" as a group member in
addition to whoever else you want to be working on bug triage.
http://docs.openstack.org/infra/manual/creators.html#create-bug-tracker
--
tom of our meeting agenda pointing people to the old URL of our
earlier meetings from before we renamed.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
rd accepted"
from NickServ on FreeNode.
...after which it began joining channels successfully again. So this
was a random problem in Freenode, or in our service provider, or
with the Internet at large. Definitely not driven by anyone
approving a configuration change while meetings were unde
avor fishbowl format more than
they have in previous cycles (we still have a week to adjust our
official allocation request).
[1]
http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-08-23-19.01.html
[2] https://etherpad.openstack.org/p/infra-ocata-summit-plannin
On 2016-08-26 00:16:12 -0300 (-0300), Sebastian Marcet wrote:
> ok Craige, once i got approval for this
> https://review.openstack.org/360862
Which merged a couple hours later at 05:12 UTC, so should presumably
be working for the past ~10 hours.
--
Jeremy S
re we have the
content moved. The ticket didn't indicate what sort of time
constraints you might be under for a resolution.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
pps_site
> 11) merge ‚glare-support’ branch to master for openstack-infra/system-config
> (in this step jenkins should put +1)
> 10) remove old apps.openstack.org
[...]
This looks basically like what we discussed in IRC last week. It
seems like a fine plan to me, and since nob
l
configuration management in these to be able to handle the
production and staging sites with the ability to specify which Git
ref you want used from app-catalog on each.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.opensta
time, and of course keep
padding the pad.
[0] https://etherpad.openstack.org/p/infra-ocata-summit-planning
[1]
http://lists.openstack.org/pipermail/openstack-dev/2016-September/103851.html
[2]
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Ag
u're satisfied with the state of feature/glare-support as
evidenced from using the dev server, merge that branch back into
master and the continuous automation you already have will make it
live on the production apps.openstack.org server.
--
Jeremy Stanley
__
eas?
[*] https://etherpad.openstack.org/p/infra-ocata-summit-planning
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
ll be working on
finalizing these). Sounds like they may put them on stickers or
other stuff in time for the PTG in Atlanta.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/ma
ture (such that release
artifacts of the donor repo might get overwritten) seems like a
sane compromise.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
nt hits for that v6 prefix, though not finding
any for the v4 one.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
On 2016-11-09 18:11:39 + (+), Jeremy Stanley wrote:
> On 2016-11-08 19:12:32 +0800 (+0800), Tom Fifield wrote:
> [...]
> > Upstream apparently revamped the spam system in the version marked
> > to upgrade to in:
> > https://review.openstack.org/#/c/274032/
>
>
On 2016-11-09 19:53:27 + (+), Jeremy Stanley wrote:
> On 2016-11-09 18:11:39 + (+), Jeremy Stanley wrote:
> > On 2016-11-08 19:12:32 +0800 (+0800), Tom Fifield wrote:
> > [...]
> > > Upstream apparently revamped the spam system in the version marke
e causing calls into the provider
to short-circuit since it always returns true if a commit or tag is
passed. The next round, I was going to try dropping that from the
commit and tag cases in puppet-askbot and seeing if it helps.
--
Jeremy Stanley
___
Op
t
is guaranteed to happen and we cannot prevent that (nor would we
want to).
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
r/doc/source/third_party_ci.rst
The rendered version is continuously published at:
http://docs.openstack.org/infra/openstackci/
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mail
ating these daily at midnight UTC (doesn't
seem to be logrotate doing it) isn't compressing them, so they're up
to nearly 13GB now (which is a lot on a 40GB rootfs).
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.opens
rators group. I take it they're not visible for you?
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
7;re looking for. What kind of
documentation do you have in mind? We don't make Gerrit, so we rely
on the documentation written by the people who do. What is it
missing that you want it to cover?
--
Jeremy Stanley
___
OpenStack-Infra mailing
al routes in
some service providers (namely OSIC). Kevin Benton addressed this
with change https://review.openstack.org/398012 to DevStack adding
an optional setting which will be consumed by Monty's change
https://review.openstack.org/398611 to devstack-gate (hopefully to
merge within the next
C on Wednesdays in #openstack-meeting
[...]
Just following up, I approved this out of the moderation backlog but
suspect it's a duplicate (at any rate that's why it's dated from a
few weeks ago).
--
Jeremy Stanley
___
OpenStack-Infr
ordering. I've briefly
searched/skimmed and am not spotting any if so. Unfortunate.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
to all who attended, and to those who could not: we missed
you. I hope to see lots of you again at the PTG in Atlanta, only a
couple months away now. Don't forget to register and book your
flights/lodging!
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
ble path forward?
I have a strong preference for the proposed model, as it still
allows for differing label-to-flavor mapping per provider while
simplifying the relationship between providers, images and flavors
compared to the old nodepool~=0.3 implementation.
--
Jeremy Stanley
er we can remove them entirely the better.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
spike caused by that deletion? Or was the deletion
error coincidental and caused by a memory event which just happened
to be going on at the same time? I have insufficient knowledge of
the system to be able to say either way. It's possible there are
additional logs I don't know t
;t have much insight into reader
expectations). Is the longer-term plan to review analytics for page
hits against docs-archive to figure out what else should be copied
over to docs.o.o manually, or incorporated/reintroduced into
documentation builds?
--
Jeremy Stanley
___
vent (nor
can I find anything to correlate it to in syslog, Apache error logs,
Askbot application logs, Solr/Jetty request or stderrout logs, et
cetera).
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
On 2017-01-02 23:03:07 + (+), Jeremy Stanley wrote:
[...]
> We're basically ready to retry the previous upgrade now that some
> issues have been identified/corrected by Marton. Change
> https://review.openstack.org/408657 to trigger it is waiting on
> https://review.openst
ything in the system
logs that would indicate we ran anything that would paralyze the
system like that.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
ll inconvenient, then we can work
to improve dev/production symmetry or safely increase debugging data
availability for production as needed.
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-Infra mailing list
OpenStack-I
[...]
I have added you as the initial member of both requested groups (as
the creator of the https://review.openstack.org/391593 change which
originally added them). You should now be able to add/remove other
members as needed.
--
Jeremy Stanley
___
O
p, so in the
> example of trove-core, you need to ask the trove PTL for the
> rights.
[...]
I believe he linked the trove-core group in error. I assumed he
meant https://review.openstack.org/#/admin/groups/1648,members
instead.
--
Jeremy Stanley
try to have someone with
some Infra-sense pop in and help.
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
an reenqueue the ref for it into the
post pipeline on request.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
date that if interested and then we can figure out what will
> work using that info.
Thanks for getting this idea rolling! Now I just need to find a
Hawaiian shirt... ;)
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.ope
in CPU, memory or disk activity so it
doesn't seem to be resource starvation (at least not for any common
resources we're tracking).
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
out agreeing to a CLA, as reviewing is not
considered a copyrightable contribution to the source itself (even
though reviewers do include sample source code in their comments
from time to time).
--
Jeremy Stanley
signature.asc
Description: Digital signat
y asked me to convey her personal thanks to everyone
who participated in this selection and review process.
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.o
ty, huge thanks for arranging this for us!
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
h, and we'll attempt to coordinate some work in IRC
as well for people who want to chip in remotely on tasks that don't
need much face-to-face bandwidth. I don't know how well it'll work
out in practice, but it's worth a try anyway.
--
Jeremy Stanley
__
eams you believe should have
included you in their electorate? The election officials should be
able to double-check the rolls and see if there's any discrepancy.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.opens
nce/projects.yaml?h=jan-2017-elections#n2152
And this contribution should have resulted in you being on the roll
for the Neutron PTL election:
https://review.openstack.org/401349
I've Cc'd the election officials so they can double-check their copy
of the rolls.
--
J
ddresses did appear in the rolls for that election,
is it possible that the huawei.com mailservers rejected E-mail from
c...@cs.cornell.edu (the election polling system we use)?
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.o
lections than going to conferences (or in some
cases scalping free tickets as a money-making scheme).
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
the -dev ML in case they have
previously unvoiced concerns. I'd also like to be certain the
current DIB contributors are entirely disinterested in forming a
separate official team in OpenStack as I doubt the TC would reject
such a proposal (I'd happily support it).
--
Jeremy Stanley
sign
meeting schedule.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
provide for last-minute objections
and so that my code review vote on the governance change can
accurately represent the will of the Infra team.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists
messages bound for the server will
queue at the senders' MTAs until the server is back in service and
so should not result in any obvious disruption.
Apologies for cross-posting so widely, but we wanted to make sure
copies of this announcement went to most of our higher-traffic
lists.
--
J
://storyboard.openstack.org/#!/project/731
But in this case the issue is (we think) already solved, so I
wouldn't bother filing a defect report about it at this point.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstac
from what it expects to be able to
guess when and where to add floating IPs.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
ttp://git.openstack.org/cgit/openstack-infra/shade/tree/shade/meta.py?h=1.19.0#n113
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
tack-infra@lists.openstack.org mailing list or in the
#openstack-infra IRC channel on Freenode if you have any questions.
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstac
>
> One step closer to dropping puppet from our image build process.
Also, this brings the images we're using much closer to potential
reusability outside our CI system since people no longer need to
doctor them to remove our default admin a
need any help proposing those changes into Gerrit, we're easy
to find in the #openstack-infra channel on Freenode too and always
happy to help out.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.
"#endmeeting"
> first.
[...]
After 60 minutes from the time of the #startmeeting, the meetbot
will accept a #endmeeting from anyone, even if they're not chairing.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstac
to eat, even if we just limit it to
the Back Bay and Fenway vicinity... but I'm guessing we have locals
who can make better suggestions than I could ever hope to provide.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.opensta
On 2017-04-29 08:29:58 +0200 (+0200), Yolanda Robla Mota wrote:
> Unfortunately I won't be coming to the summit this time... Enjoy!
[...]
We'll miss you!
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.opens
On 2017-05-04 11:30:57 -0400 (-0400), Paul Belanger wrote:
[...]
> date and time is 8:00pm on Monday for http://thesaltypig.com/.
>
> I suggest maybe we meet at the summit mixer and walk over to the
> restaurant together.
[...]
Sounds great--thanks for organizing!
--
Je
d OSF
for picking up the tab)!
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
g update for that section of the document which
should correct it once approved:
https://review.openstack.org/461498
See if the updated text in that patch works for you.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.o
on it.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
to try the beta versions (it looks
like there's been quite a few new commits in master over the past
couple months, so maybe it's time for either 2.0.0.0b3 or even
2.0.0.0rc1?).
All that said, I'm not really an active developer on JJB so the dev
team members on it may h
will queue at the senders' MTAs
until the server is back in service and so should not result in any
obvious disruption.
Apologies for cross-posting so widely, but we wanted to make sure
copies of this announcement went to most of our higher-traffic
lists.
--
Jeremy Stanley
signatur
On 2017-05-24 16:04:20 -0700 (-0700), James E. Blair wrote:
[...]
> How does that sound?
I ain't afraid of no ghosts. Let's do it!
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-Infra mailing list
Op
bout anything. Would having a
generic HTTP(S) driver for things like this make sense?
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
oads, so when the time comes to stop supporting the old
syntax we can also see about rejecting new patchsets which are using
the then-unsupported format (as long as the error can be clearly
passed through the likes of git-review so users aren't too
confused).
--
Jeremy Stanley
signatu
On 2017-05-25 08:10:33 -0700 (-0700), James E. Blair wrote:
> Jeremy Stanley writes:
[...]
> > Alternative/complimentary idea, Gerrit hooks can also be used to
> > reject uploads, so when the time comes to stop supporting the old
> > syntax we can also see about rejecting ne
versions of those images
is unnecessary. If you need a periodic job to upload and replace
pregenerated branch-tip snapshot images for consumption by other CI
jobs, we should be able to work something out pretty easily (that's
what the other projects I mentioned above have been doing)
hing similar
to that). The use cases, storage needs and security/support concerns
are vastly different.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
agree a general
logset per changeish might be nice in addition to per-job logs and
this information might fit well somewhere there (or copied into each
build result).
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.or
ice of
> creating a separate pipeline for push like events from change like
> events. I welcome other opinions!
This seems like a reasonable conclusion to me.
--
Jeremy Stanley
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://l
On 2017-05-30 12:49:37 +0200 (+0200), Luigi Toscano wrote:
> On Friday, 26 May 2017 15:27:02 CEST Jeremy Stanley wrote:
[...]
> > We can see about extending the available free space for
> > tarballs.openstack.org after we relocate it off the same server
> > where we store
.org/irclogs/%23openstack-infra/%23openstack-infra.2017-06-09.log.html#t2017-06-09T15:32:27-2
>
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.open
m? At the moment (at least until we upgrade Gerrit again)
the Infra team still needs to delete branches, but ACLs for pushing
signed tags can certainly be added however you need.
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenSt
; puppet-swift
> > puppet-tempest
> > puppet-trove
> > puppet-vswitch
> > puppet-zaqar
[...]
It looks like these are covered by Tony's request to the dev ML:
http://lists.openstack.org/pipermail/openstack-dev/2017-June/118473.html
Please confirm you don't need a
I would classify missing chain certs as a known issue, but one
you'll need to address on your end. Alternatively, you could switch
to using an http:// scheme in the planet config for your
syndication since you're apparently not unilaterally r
-specs/specs/puppet-module-functional-testing.html
[5]
http://specs.openstack.org/openstack-infra/infra-specs/specs/puppet_4_prelim_testing.html
[6] https://review.openstack.org/449933
[7] https://review.openstack.org/469983
--
Jeremy Stanley
signature.asc
Description: Digital signature
to
it before then I can't really commit to it until I'm around again
either.
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
board, or
> is this not in your domain?
The www.openstack.org site is not under the care of the community
infrastructure sysadmins. You can notify the OpenStack Foundation
Web devs by filing a bug report here:
https://bugs.launchpad.net/openstack-org/+filebug
--
Jeremy Stanley
signatu
which you were the change author, so this request is sufficient.
I have now added you to both groups.
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstac
I just posted an announcement to openstack-dev which is also
relevant to some subscribers of this ML who may not see it there:
http://lists.openstack.org/pipermail/openstack-dev/2017-July/119786.html
If possible, please follow up there with any questions.
--
Jeremy Stanley
signature.asc
wizardry you haven't tried, they haven't chimed in to suggest
it either.
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
1 - 100 of 682 matches
Mail list logo
