[rdo-list] TripleO images deleted from CentOS artifacts server
by John Trowbridge
I have received a few emails and a few patches wrt $subject, so I will
respond on this list instead of individually.
Last night, sometime around midnight UTC, the entire rdo/images
directory was deleted from the CentOS artifacts server. I have asked
folks on #centos-devel if this was intentional, and it was not. However,
we don't have a root cause for how it happened yet.
Luckily, we had the images mirrored to the CDN for liberty and mitaka,
and I had a local image for master. I have manually re-uploaded all
images to the artifacts server.
I will update this thread, when/if there is more details as to the root
cause.
-trown
8 years, 8 months
[rdo-list] Fwd: [CentOS-devel] Important infra outage notification - dates to be discussed
by Alan Pevec
Hi,
sending to the list for heads-up, we'll discuss it on weekly meeting next week.
Looking at upstream schedule[1] and our proposed testdays[2] one
weekend in mid-June should be least worst time for this outage.
Cheers,
Alan
[1] http://releases.openstack.org/newton/schedule.html
[2] https://www.rdoproject.org/testday/
---------- Forwarded message ----------
From: Fabian Arrotin <arrfab(a)centos.org>
Date: Fri, May 20, 2016 at 10:27 AM
Subject: [CentOS-devel] Important infra outage notification - dates to
be discussed
To: "The CentOS developers mailing list." <centos-devel(a)centos.org>,
"ci-users(a)centos.org" <ci-users(a)centos.org>
Due to some reorganization at the DC/Cage level, we'll have to
shutdown/move/reconfigure a big part of our hosted infra for the
following services :
- cbs.centos.org (Koji)
- accounts.centos.org (auth backend)
- ci.centos.org (jenkins-driven CI environment)
We're working on a plan to minimize the downtime/reconfiguration part,
but at first sight, due to the hardware move of the racks/recabling
parts/etc, the announced downtime will be probably ~48h.
What does that mean ? That during this window, nobody will be able to
build/tests packages, nor be able to triggers automatically CI jobs
(important).
As said, we're working on an agenda with the team operating the DC, but
we'd like you (cbs and ci users) to give us feedback on the best (or
worst ?) time line for such migration.
For example if you know that your $project will have a release soon, and
already have an agenda for such release (and so build/ci) and that you
rely on that infra, we'd like you to communicate those informations to
us, so that we can try to find the best possible time slot for the
migration, minimizing the impact on the whole CentOS ecosystem (and so
for all our users)
Feel free to answer in this thread, or find us in #centos-devel on freenode.
--
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
_______________________________________________
CentOS-devel mailing list
CentOS-devel(a)centos.org
https://lists.centos.org/mailman/listinfo/centos-devel
8 years, 8 months
[rdo-list] How to assign two same type PCI pass-through devices (Ethernet cards) to 2 different VM instances?
by Chinmaya Dwibedy
Hi All,
Can we assign two same type PCI pass-through devices (Ethernet cards) to 2
different VM instances separately? Please note that, both the cards have
same vendor_id and product_id.
I configured it in pci_passthrough_whitelist and create two different
pci_alias (Say a1 and a2). Modified the Nova flavor to use a1 by VM1 and
VM2. Followed the procedures mentioned at
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/...
With this edited xml files of both the instances (after shutting down).
Added a device entry in the <source> section to assign the PCI device to
the guest virtual machine. and accordingly configured domain, bus, slot and
function. Restarted the VMs using #virsh start command. Made an Query pci
device in nova DB and found that two Ethernet PCI devices have been
assigned to single VM.
I cannot assign 2 same type PCI pass-through Ethernet devices to 2 VM
instances separately. Can you please let me know how to accomplish the
same? Thanks in advance for your time and help.
Regards,
Chinmaya
8 years, 8 months
[rdo-list] [Meeting] RDO meeting (2016-05-18) Minutes
by Javier Pena
==============================
#rdo: RDO meeting (2016-05-18)
==============================
Meeting started by jpena at 15:00:51 UTC. The full logs are available at
https://meetbot.fedoraproject.org/rdo/2016-05-18/rdo_meeting_(2016-05-18)...
.
Meeting summary
---------------
* roll call (jpena, 15:00:59)
* Comment for EOL Bugs (jpena, 15:05:09)
* LINK: https://wiki.openstack.org/wiki/Releases (rbowen, 15:06:46)
* LINK: http://releases.openstack.org/ (chandankumar, 15:06:53)
* ACTION: chandankumar to share EOL script with imcsk8 and others for
review. (chandankumar, 15:09:56)
* EOL message for RDO bugzillas "This bug is against a version which
has reached End of Life. Please reopen if it is still relevant with
a latest version: http://releases.openstack.org/" (apevec,
15:12:26)
* move rdostats project under RDO (jpena, 15:15:00)
* LINK: https://github.com/larsks/rdostats (chandankumar, 15:15:53)
* ACTION: larsks to be asked nicely to migrate
https://github.com/larsks/rdostats to rdo-infra (apevec, 15:21:17)
* Hangouts - speakers wanted (jpena, 15:22:32)
* DLRN instance migration to ci.centos infra (reloaded) (jpena,
15:25:02)
* ACTION: trown submit patch to tripleoci to change repo promotion
method (trown, 15:29:37)
* ACTION: dmsimard to set up ssh authentication between the
ci.centos.org slave and dlrn instance (dmsimard, 15:31:45)
* chair for next meeting (dmsimard, 15:31:50)
* ACTION: imcsk8 to chair next meeting (jpena, 15:32:08)
* open floor (jpena, 15:32:42)
* ACTION: apevec to send bz request to update RDO versions in bz
(apevec, 15:35:51)
Meeting ended at 15:41:30 UTC.
Action Items
------------
* chandankumar to share EOL script with imcsk8 and others for review.
* larsks to be asked nicely to migrate
https://github.com/larsks/rdostats to rdo-infra
* trown submit patch to tripleoci to change repo promotion method
* dmsimard to set up ssh authentication between the ci.centos.org slave
and dlrn instance
* imcsk8 to chair next meeting
* apevec to send bz request to update RDO versions in bz
Action Items, by person
-----------------------
* apevec
* apevec to send bz request to update RDO versions in bz
* chandankumar
* chandankumar to share EOL script with imcsk8 and others for review.
* dmsimard
* dmsimard to set up ssh authentication between the ci.centos.org
slave and dlrn instance
* imcsk8
* chandankumar to share EOL script with imcsk8 and others for review.
* imcsk8 to chair next meeting
* trown
* trown submit patch to tripleoci to change repo promotion method
* **UNASSIGNED**
* larsks to be asked nicely to migrate
https://github.com/larsks/rdostats to rdo-infra
People Present (lines said)
---------------------------
* jpena (41)
* apevec (38)
* dmsimard (38)
* chandankumar (31)
* zodbot (17)
* rbowen (16)
* tristanC (12)
* imcsk8 (12)
* trown (7)
* leifmadsen (6)
* rdogerrit (4)
* openstack (4)
* amoralej (2)
* misc (2)
* gkadam (2)
* jruzicka (2)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
8 years, 8 months
[rdo-list] [tripleo] How to setup hyper-converged nodes (compute+ceph)?
by Gerard Braad
Hi All,
currently looking into TripleO and see if it is possible to use it to
deploy a hyper-converged infrastructure. In our cases, we would like
to deploy Compute nodes with Ceph installed on them. This will
probably be a change to the tripleo-heat-templates and the compute,
and cephstorage resources? Which changes are needed to accomplish
this..
regards,
Gerard
--
Gerard Braad — 吉拉德
F/OSS & IT Consultant
http://gbraad.nl
8 years, 8 months
[rdo-list] [TripleO][QuickStart] 2 fixable problems in tripleo-quickstart - CentOS7.2
by Marcos Garcia
Hello all
Today I've tested https://github.com/openstack/tripleo-quickstart/ on a
fresh CentOS 7.2 (hosted server, 32 GB RAM)
These are well-known problems that I've found on CentOS forums, not
precisely new, but I thought you may all be interested in knowing that
these block the installation of tripleo-quickstart at certain points (first
at the undercloud VM creation, second at the initial steps of overcloud
deploy)
Maybe you want to add a comment in the documentation?
1. #ERROR: qemu-kvm: -chardev pty,id=charserial0: Failed to create
chardev\n
1. I solved it via
https://loginroot.com/qemu-kvm-chardev-ptyidcharserial0-failed-to-create-...
2. Basically, replace the devpts line of /etc/fstab with “*devpts
/dev/pts devpts gid=5,mode=620 0 0*“
3. Then do “*mount -o remount /dev/pts*“
2. #ERROR: Node 141e60b7-19ea-43d1-b14e-fe07193cdf7d did not pass power
credentials validation: SSH connection cannot be established: Failed to
establish SSH connection to host 192.168.23.1 ; and DEBUG
ironic.common.utils [req-8d62ae59-8832-4eec-82d6-c9139d7624a8 – – – – -]
SSH connect failed: Incompatible ssh server (no acceptable macs)
ssh_connect /usr/lib/python2.7/site
1. I solved it via
http://stackoverflow.com/questions/28399335/python-paramiko-incompatible-...
2. Just edit /etc/ssh/sshd_conf and add another MAC algorithm: *MACs
hmac-sha1*
3. Then, restart the service with *systemctl restart sshd*
I was also very annoyed by the lack of "virsh list --all" as root - as
documented here
https://github.com/openstack/tripleo-quickstart/blob/master/docs/accessin....
It should be also commented beforehand, IMO :)
Other than those two problems, the installation went very smoothly. It took
much more space than I expected (like 31GB in /home space in the $VIRTHOST).
Good job guys :)
PS: I wrote the end-to-end installation on my personal blog
https://simplenfv.wordpress.com/2016/05/16/deploying-openstack-on-just-on...
--
Marcos Garcia
*NFV and Openstack Technical Marketing Manager*
mgarciam(a)redhat.com
Red Hat Canada
Every telecommunications company in the Fortune Global 500 relies on Red
Hat.
Find out why at Trusted | Red Hat <http://www.redhat.com/en/about/trusted>
8 years, 8 months
