pond with any comments or concerns.
>
> Thanks, Elizabeth, for all your work!
>
> -Jim
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack
loud/A-new-model-to-deliver-public-cloud/ba-p/6804409#.VqgUMF5VKlM
[2]
http://lists.openstack.org/pipermail/openstack-infra/2015-December/003554.html
[3] https://wiki.openstack.org/wiki/Sprints/InfraMitakaSprint
--
Cody A.W. Somerville
___
OpenStack-Inf
HPE provides a number of baremetal nodes in two of their public cloud data
centers, referred to as "US East" and "US West", for the infracloud
project. As part of the sunset of HPE's public cloud, this hardware needs
to be relocated. HPE has determined both sets of hardware will be relocated
to the
tion: Agreed that Richard can begin de-rack and ship process after EOD
February 25th.
- Prioritize SL390 if possible from US West.
--
Cody A.W. Somerville
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org
mation passively and will follow-up via IRC or
e-mail with individuals as necessary such as with those who can provide
status updates for HPE. Will use etherpad prior to e-mailing the report to
permit folks to help with contributing or editing if interested.
Cheers,
Cody
eview.openstack.org/#/c/267863/
--
Cody A.W. Somerville
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
So I've just shot off the first weekly update. It's format is pretty basic
for now but will evolve it as needed/as is helpful.
I'll also work with folks to identify some major milestones to track
progress against.
--
Cody A.W. Somerville
__
gt;
2. Add roles for CI users <https://review.openstack.org/288160>
--
Cody A.W. Somerville
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
changes merged under infra-cloud topic since last weekly
report.
--
Cody A.W. Somerville
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 4) keep 10.10.16.0/24 for internal network
> >
> > 5) Do we need nic bonding?
> > - no
> >
Agreed. I was going to make the same point.
--
Cody A.W. Somerville
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
on will be released publicly.
c. HPE networking team will begin setting up network as requested and
working with Verizon to provision requested /48 space block.
Risks:
No risks to note at this time.
Changes Merged:
No additional changes merged under infra-cloud topic since last weekly
report.
--
yond those inherent to relocation and age
of equipment (and rotational disks).
2. New network configuration requires validation.
Changes Merged:
No additional changes merged under infra-cloud topic since last weekly
report.
--
Cody A.W. Somerville
___
twork configuration requires validation.
3. Initial re-deploy of infra cloud may not be complete/ready by OpenStack
Summit.
Changes Merged:
1. Add playbook to manage power state of ironic servers
<https://review.openstack.org/284981>
--
Cody A.W.
13 matches
Mail list logo
