From 7dde0194328c5eaf92fea09784f4fa5a2d9f8ff5 Mon Sep 17 00:00:00 2001 From: Mary Thengvall Date: Mon, 15 Jan 2018 23:09:17 -0800 Subject: [PATCH 1/9] fixed all links under `/source/what/` --- source/what/promotion-pipeline.html.md | 5 ++--- source/what/release-overview.html.md | 5 ++--- source/what/repos.html.md | 2 +- source/what/workflow-overview.html.md | 4 ++-- source/what/workflow.html.md | 5 ++--- 5 files changed, 9 insertions(+), 12 deletions(-) diff --git a/source/what/promotion-pipeline.html.md b/source/what/promotion-pipeline.html.md index 2ff7302c9..2eeb1c2aa 100644 --- a/source/what/promotion-pipeline.html.md +++ b/source/what/promotion-pipeline.html.md @@ -107,12 +107,11 @@ status of RDO packaging and CI. * [TripleO quickstart demostration](https://www.youtube.com/watch?v=4O8KvC66eeU) by trown * [Weirdo: A talk about CI in OpenStack and RDO](https://dmsimard.com/2016/03/02/openstack-montreal-a-talk-about-ci-in-openstack-and-rdo/) by dmsimard. -* [ARA blog posts](https://dmsimard.com/tag/ara.html) - from dmsimard blog +* [ARA blog posts](https://dmsimard.com/categories/ara) - from dmsimard blog * [Ci in RDO: What do we test?](https://amoralej.fedorapeople.org/slides/RDO-CI-summit-bcn-final.pdf) - presentation in RDO and Ceph Meetup BCN. ---- [← Trunk repos](/what/trunk-repos) | [→ Adding packages](/what/new-package) | -[↑ TOC](/what) - +[↑ TOC](/what) diff --git a/source/what/release-overview.html.md b/source/what/release-overview.html.md index fb595a1a6..721de6e39 100644 --- a/source/what/release-overview.html.md +++ b/source/what/release-overview.html.md @@ -22,6 +22,5 @@ The following pieces of infrastructure are used for GA packages: ---- -[← Release workflow](/what/release-workflow) | -[↑ TOC](/what) - +[← Release workflow](/what/release) | +[↑ TOC](/what) diff --git a/source/what/repos.html.md b/source/what/repos.html.md index 1bcc762a6..379f46d02 100644 --- a/source/what/repos.html.md +++ b/source/what/repos.html.md @@ -64,5 +64,5 @@ If you need a package using the latest commit, even before it passes CI (be awar ## More information: * [Previous - Delivery pipeline](/what/pipeline) -* [Newbie in RDO: one size doesn't fit all](/blog/2016/05/new-in-rdo-repos-one-size-doesn-t-fit-all/) +* [Newbie in RDO: one size doesn't fit all](/blog/2016/04/new-in-rdo-repos-one-size-doesn-t-fit-all/) * [TOC](/what) diff --git a/source/what/workflow-overview.html.md b/source/what/workflow-overview.html.md index 833d8e5b0..d25405f7c 100644 --- a/source/what/workflow-overview.html.md +++ b/source/what/workflow-overview.html.md @@ -17,7 +17,7 @@ The following pieces of infrastructure are used during the cycle: - [review.rdoproject.org](https://review.rdoproject.org) is the central system for our workflow, powered by [SoftwareFactory](https://softwarefactory-project.io/docs/). It contains a Gerrit instance to manage all changes to the repositories where the spec files used to build our packages are contained, as well as the components managing our CI infrastructure. - [Our distgit repositories](https://github.com/rdo-packages) contain one repository for each project built by RDO, where the spec files are located. Every change submitted via review.rdoproject.org is synchronized to the repos at GitHub. -- [The RDO Trunk repositories](what/trunk-repos) contain the latest packages. +- [The RDO Trunk repositories](/what/trunk-repos) contain the latest packages. - [The Centos CI infrastructure](https://ci.centos.org/view/rdo/view/promotion-pipeline/) is used to run the periodic jobs to promote the latest repositories. - Our own RDO Cloud is used to host most of our infrastructure servers, as well as a pool of test VMs used by review.rdoproject.org to verify all incoming changes. @@ -25,4 +25,4 @@ The following pieces of infrastructure are used during the cycle: [← Workflow](/what/workflow) | [→ DLRN](/what/dlrn) | -[↑ TOC](/what) +[↑ TOC](/what) diff --git a/source/what/workflow.html.md b/source/what/workflow.html.md index af4d72201..8390d718d 100644 --- a/source/what/workflow.html.md +++ b/source/what/workflow.html.md @@ -8,7 +8,7 @@ While an upstream development cycle is in process, we package up what happens each day, using the following workflow. TODO For what we do once a release happens upstream, see [this -doc](release-workflow). +doc](/what/release/). * [Overview and infrastructure](/what/workflow-overview) * [DLRN: what it is, what we use it for](/what/dlrn) @@ -20,5 +20,4 @@ doc](release-workflow). [← Available Repos](/what/repos) | [→ Workflow overview](/what/workflow-overview) | -[↑ TOC](/what) - +[↑ TOC](/what) From 3cacf15bd258e2362203a777e2025a8710733abc Mon Sep 17 00:00:00 2001 From: Mary Thengvall Date: Tue, 16 Jan 2018 09:26:10 -0800 Subject: [PATCH 2/9] updated events --- data/events | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/events b/data/events index ed71d4a0e..93f026e7b 160000 --- a/data/events +++ b/data/events @@ -1 +1 @@ -Subproject commit ed71d4a0e4e090355d3d581077d80afedb5fee8c +Subproject commit 93f026e7b0fa0db56d4c065ce6cb07957e226f7f From 875fa4ccf5cd15785c0b99da4bc3b5852b725303 Mon Sep 17 00:00:00 2001 From: Mary Thengvall Date: Tue, 16 Jan 2018 13:30:54 -0800 Subject: [PATCH 3/9] links fixed for `source/blog/` files --- source/blog/2013-04-13-announcing-rdo.html.md | 6 +++--- source/blog/2013-05-02-rdo-in-the-news.html.md | 2 +- .../2013-06-05-try-out-rdo-on-trystack.html.md | 4 ++-- .../2013-07-03-rdo-community-newsletter.html.md | 4 ++-- .../2013-07-26-ceph-for-cinder-on-rdo.html.md | 10 ---------- .../2013-09-02-a-tour-of-openstack-blogs.html.md | 5 +++-- ...ents-next-week-test-day-google-hangout.html.md | 2 +- .../blog/2014-03-04-rdo-march-newsletter.html.md | 6 +++--- ...-rdo-meetup-openstack-summit-vancouver.html.md | 2 +- .../blog/2015-10-14-rdo-test-day-summary.html.md | 4 ++-- ...o-liberty-released-in-centos-cloud-sig.html.md | 7 +++---- ...-rdo-mitaka-3-test-day-march-10th-11th.html.md | 6 +++--- ...6-upcoming-events-in-openstack-and-rdo.html.md | 3 +-- ...rdo-2-rdo-trunk-from-a-bird-s-eye-view.html.md | 2 +- .../blog/2016-04-12-rdo-mitaka-released.html.md | 10 +++++----- ...ement-migration-to-reviewrdoprojectorg.html.md | 2 +- .../blog/2016-06-08-june-rdo-newsletter.html.md | 4 ++-- ...ck-days-budapest-openstack-days-prague.html.md | 15 +++++++-------- .../blog/2016-10-04-rdo-newton-released.html.md | 6 +++--- ...16-10-05-how-to-run-rally-on-packstack.html.md | 2 +- ...-22-chasing-the-trunk-but-not-too-fast.html.md | 2 +- .../blog/2017-03-16-rdo-ci-in-a-nutshell.html.md | 2 +- ...fully-automated-GUI-tests-in-the-cloud.html.md | 14 +++++++++----- .../2017-08-01-rdopkg-0.44-changeblog.html.md | 6 ++++-- ...ack-3rd-party-ci-with-software-factory.html.md | 6 +++--- 25 files changed, 63 insertions(+), 69 deletions(-) delete mode 100644 source/blog/2013-07-26-ceph-for-cinder-on-rdo.html.md diff --git a/source/blog/2013-04-13-announcing-rdo.html.md b/source/blog/2013-04-13-announcing-rdo.html.md index 215cd75cb..1cf6beabd 100644 --- a/source/blog/2013-04-13-announcing-rdo.html.md +++ b/source/blog/2013-04-13-announcing-rdo.html.md @@ -9,11 +9,11 @@ Today, we are releasing OpenStack Grizzly packages for Red Hat Enterprise Linux And to help you make the most of OpenStack, we've created this site so you can: -* Connect with fellow OpenStack users on the [community forums](/forum); +* Connect with fellow OpenStack users on the [mailing lists](https://www.rdoproject.org/contribute/mailing-lists/) or in the #rdo channel on the [Freenode](http://freenode.net/) server; * [Get started](/install/packstack/) with the latest OpenStack project software, packaged and ready to use on Red Hat Enterprise Linux, CentOS, Scientific Linux, Fedora, and other RHEL derivatives and Fedora remixes; -* Read and improve on our [documentation](/documentation), check the [troubleshooting page](/troubleshooting/) if you have any issues, and consider adding your OpenStack set-up as a [case study](/user-stories) +* Read and improve on our [documentation](https://www.rdoproject.org/use/), check the [troubleshooting page](/troubleshooting/) if you have any issues, and consider adding your OpenStack set-up as a [case study](/user-stories) -If you have any questions, feel free to ask your questions here. And if you see a great nugget of information you want to share with others, consider adding it to our [wiki](http://rdoproject.org/Adding_new_content). As always, it's the community behind open source projects that makes them great and we are excited to invite everyone in. +If you have any questions, take a look at our [Ask and Answer](https://www.rdoproject.org/contribute/#ask-and-answer) section of the site. And if you see a great nugget of information you want to share with others, feel free to send it to the [mailing lists](https://www.rdoproject.org/contribute/mailing-lists/). As always, it's the community behind open source projects that makes them great and we are excited to invite everyone in. Thanks, and have fun with OpenStack! Dave Neary diff --git a/source/blog/2013-05-02-rdo-in-the-news.html.md b/source/blog/2013-05-02-rdo-in-the-news.html.md index a9dcbf6b4..7e1286edd 100644 --- a/source/blog/2013-05-02-rdo-in-the-news.html.md +++ b/source/blog/2013-05-02-rdo-in-the-news.html.md @@ -11,7 +11,7 @@ Since launching on April 15th, RDO has garnered a lot of attention - both in pre In Portland during [the OpenStack Summit](https://www.openstack.org/summit/portland-2013/) Dave Neary sat down with Richard Morrell of Red hat to record a podcast, covering questions like "what is RDO?", "who is it for?" "why are Red Hat releasing a community distribution of OpenStack?" -Hear the answers to these questions and more [at the Cloud Evangelist website](http://cloudevangelist.org/2013/04/17/podcast-openstack-developer-summit-2013/) +Hear the answers to these questions and more [at the Cloud Evangelist website](http://thecloudevangelist.com/cloud-software/podcast-openstack-developer-summit-2013/) ## OpenStack Summit review diff --git a/source/blog/2013-06-05-try-out-rdo-on-trystack.html.md b/source/blog/2013-06-05-try-out-rdo-on-trystack.html.md index 5f760dcfa..bb18c0e19 100644 --- a/source/blog/2013-06-05-try-out-rdo-on-trystack.html.md +++ b/source/blog/2013-06-05-try-out-rdo-on-trystack.html.md @@ -15,6 +15,6 @@ anyone can register and try out OpenStack. [The x86 OpenStack cluster at TryStack.org](http://x86.trystack.org) runs on RHEL 6.4 and thanks to some awesome work from Dan Radez we have recently completed the upgrade to the Grizzly release using packages from RDO. Red Hat has committed to the ongoing support and maintenance of the x86 cluster. -Head over to [TryStack.org](http://trystack.org) now to register for an account, and [try out RDO for your self](http://rdoproject.org/Using_RDO_on_TryStack). +Head over to [TryStack.org](http://trystack.org) now to register for an account, and [try out RDO for your self](https://www.rdoproject.org/documentation/trystack/ ). -For more information on getting started with RDO on your own servers, visit rdoproject.org and [download the packages today](http://rdoproject.org/Quickstart). +For more information on getting started with RDO on your own servers, visit rdoproject.org and [download the packages today](https://www.rdoproject.org/install/). diff --git a/source/blog/2013-07-03-rdo-community-newsletter.html.md b/source/blog/2013-07-03-rdo-community-newsletter.html.md index 71d0a1d49..bd0b07a9e 100644 --- a/source/blog/2013-07-03-rdo-community-newsletter.html.md +++ b/source/blog/2013-07-03-rdo-community-newsletter.html.md @@ -7,6 +7,6 @@ tags: newsletter In case you missed it, the inaugural edition of the RDO Community Newsletter may be read at https://www.redhat.com/archives/rdo-newsletter/2013-July/msg00000.html -If you didn't receive it and would like to receive the next one, you can can subscribe at https://www.redhat.com/mailman/listinfo/rdo-newsletter +If you didn't receive it and would like to receive the next one, you can can subscribe at https://lists.rdoproject.org/mailman/listinfo/newsletter -If there's something you think we should cover in the August newsletter, please let us know. \ No newline at end of file +If there's something you think we should cover in the August newsletter, please let us know. diff --git a/source/blog/2013-07-26-ceph-for-cinder-on-rdo.html.md b/source/blog/2013-07-26-ceph-for-cinder-on-rdo.html.md deleted file mode 100644 index d7bfbc041..000000000 --- a/source/blog/2013-07-26-ceph-for-cinder-on-rdo.html.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Ceph for Cinder on RDO -date: 2013-07-26 16:08:35 -author: dneary -tags: ceilometer, storage, cinder, answered ---- - -Our friends in Inktank recently added a new page to the wiki [documenting the process for enabling Ceph for block storage on RDO](http://rdoproject.org/Using_Ceph_for_Block_Storage_with_RDO). - -This has been a popular request from RDO users in addition to the documentation and support for [Gluster as a storage back-end](http://www.gluster.org/community/documentation/index.php/GlusterFS_Cinder). Let us know how it works! diff --git a/source/blog/2013-09-02-a-tour-of-openstack-blogs.html.md b/source/blog/2013-09-02-a-tour-of-openstack-blogs.html.md index 5d5ec04e3..2992c7823 100644 --- a/source/blog/2013-09-02-a-tour-of-openstack-blogs.html.md +++ b/source/blog/2013-09-02-a-tour-of-openstack-blogs.html.md @@ -10,11 +10,12 @@ Recently there have been some great articles appearing describing how to do some * For those following the very hot "OpenStack Core" discussions, you might be interested in Rob Hirschfeld's series [what is Core](http://robhirschfeld.com/2013/07/22/kicking-off-core/) * For people using Swift as an object store, the experiences of Spil Games [using OpenStack Swift with lots of small files](http://engineering.spilgames.com/openstack-swift-lots-small-files/) will make for a good read + +Keep them coming! And if you want to get regular email updates from the world of RDO, [sign up to our monthly newsletter](https://lists.rdoproject.org/mailman/listinfo/newsletter). diff --git a/source/blog/2013-10-25-rdo-events-next-week-test-day-google-hangout.html.md b/source/blog/2013-10-25-rdo-events-next-week-test-day-google-hangout.html.md index 3dfcebc20..0a592dcc7 100644 --- a/source/blog/2013-10-25-rdo-events-next-week-test-day-google-hangout.html.md +++ b/source/blog/2013-10-25-rdo-events-next-week-test-day-google-hangout.html.md @@ -7,6 +7,6 @@ tags: events We've got two events next week you'll want to put on your calendars. -On Tuesday and Wednesday (October 29th and 30th) we'll be doing another [RDO Test Day](http://rdoproject.org/RDO_Test_Day_October_2013), where we'll be putting the Havana release through its paces. We'd really appreciate a few hours of your time to help make sure that the new release is solid. +On Tuesday and Wednesday (October 29th and 30th) we'll be doing another [RDO Test Day](https://www.rdoproject.org/testday/), where we'll be putting the Havana release through its paces. We'd really appreciate a few hours of your time to help make sure that the new release is solid. Then, on Thursday (October 31st), at 4pm GMT, Brent Eagles will giving a talk about more advanced networking techniques on OpenStack. You can sign up on the [Google Hangout](https://plus.google.com/events/cfgnq5t8it7uvksrtpd00s2fcmg), and attend online. diff --git a/source/blog/2014-03-04-rdo-march-newsletter.html.md b/source/blog/2014-03-04-rdo-march-newsletter.html.md index 0cb1e6aac..9e136e839 100644 --- a/source/blog/2014-03-04-rdo-march-newsletter.html.md +++ b/source/blog/2014-03-04-rdo-march-newsletter.html.md @@ -14,13 +14,13 @@ Last week, Lars Kellogg-Stedman hosted a Google Hangout in which he talked about When last I wrote, I was in Belgium attending FOSDEM. That event was fantastic, and a little overwhelming, with over 5000 Free/Libre/OpenSource Software enthusiasts descending on the University of Brussels to celebrate and learn about various software projects and the issues surrounding them. While there, I interviewed Ohad Levy, who works on deploying OpenStack with The Foreman, about his work. Unfortunately, I managed to turn off the recorder before we started talking, and I have nothing to show for it. We'll be having that conversation again over the phone in the coming days, and I'll publish that on the RDO website. -Additionally, I attended Configuration Management Camp - [cfgmgmtcamp.eu/](http://cfgmgmtcamp.eu/) - and Infrastructure.next - [lanyrd.com/2014/infranext/](http://lanyrd.com/2014/infranext/) - in Ghent, which focused on issues that are important to us in the OpenStack world - configuration management, automation, and monitoring. +Additionally, I attended Configuration Management Camp - [cfgmgmtcamp.eu/](http://cfgmgmtcamp.eu/) - and Infrastructure.next in Ghent, which focused on issues that are important to us in the OpenStack world - configuration management, automation, and monitoring. Last weekend, RDO had a table at SCaLE - the Southern California Linux Expo - [socallinuxexpo.org/blog/scale-12x](http://www.socallinuxexpo.org/blog/scale-12x) - where we had steady traffic through the whole event, with people telling us how much they love RDO, and other folks asking a lot of great questions about OpenStack, and where it fits into the larger cloud ecosystem, including projects like oVirt and OpenShift, who were our neighbors in our booth. **Upcoming events** -We are planning our next RDO Test Days on March 19th and 20th. We'll be testing the third Icehouse milestone in preparation for the final release of Icehouse on April 17th. You can find more about the test day, and sign up to participate, at [rdoproject.org/RDO_test_day_Icehouse_milestone_3](http://rdoproject.org/RDO_test_day_Icehouse_milestone_3) +We are planning our next RDO Test Days on March 19th and 20th. We'll be testing the third Icehouse milestone in preparation for the final release of Icehouse on April 17th. You can find more about the test day, and sign up to participate, at [rdoproject.org/RDO_test_day_Icehouse_milestone_3](/testday/). We'll be hosting another Google Hangout on Thursday, March 27th. Flavio Parcoco will be telling us about the Marconi project - [https://wiki.openstack.org/wiki/Marconi](https://wiki.openstack.org/wiki/Marconi) - what it is, what the plans are for the coming releases, and how you can get involved in the development of this new piece of OpenStack infrastructure. That presentation will be streamed live at [https://plus.google.com/u/1/events/ckjhm8rggnqvrnspftna845kubk](https://plus.google.com/u/1/events/ckjhm8rggnqvrnspftna845kubk) and also recorded there for viewing afterwards. @@ -48,7 +48,7 @@ And finally, you can adjust your subscription to this newsletter, or invite your Thanks again for being part of the RDO community. We look forward to seeing your contibutions. --- +-- Rich Bowen, for the RDO community rbowen@redhat.com [rdoproject.org/](http://rdoproject.org/) diff --git a/source/blog/2015-05-26-rdo-meetup-openstack-summit-vancouver.html.md b/source/blog/2015-05-26-rdo-meetup-openstack-summit-vancouver.html.md index 534f993b9..6dd251528 100644 --- a/source/blog/2015-05-26-rdo-meetup-openstack-summit-vancouver.html.md +++ b/source/blog/2015-05-26-rdo-meetup-openstack-summit-vancouver.html.md @@ -12,7 +12,7 @@ The complete agenda can be seen in the [meeting etherpad](https://etherpad.opens * Perry Myers talked some about the packaging effort - the status, and where people can get involved in that. Several people in attendance expressed a desire to get more involved. There was also some talk about how we are going to handle packaging for Fedora in the future. -* Jaromir Coufal gave an overview of the [RDO-Manager](https://www.rdoproject.org/RDO-Manager) project, which is the effort to build an installer/manager for your RDO OpenStack cloud, based on TripleO and other OpenStack projects. +* Jaromir Coufal gave an overview of the RDO-Manager project, which is the effort to build an installer/manager for your RDO OpenStack cloud, based on TripleO and other OpenStack projects. * There was some discussion around what will be included in future packaging of RDO - for example, whether it will include the newly minted projects such as [Murano](https://wiki.openstack.org/wiki/Murano), [Congress](https://wiki.openstack.org/wiki/Congress), [Mistral](https://wiki.openstack.org/wiki/Mistral), and so on. The consensus appears to be that this is up to who steps up to do that work, and so is another incentive to get more people involved in packaging. diff --git a/source/blog/2015-10-14-rdo-test-day-summary.html.md b/source/blog/2015-10-14-rdo-test-day-summary.html.md index 05c4eec39..05469dd90 100644 --- a/source/blog/2015-10-14-rdo-test-day-summary.html.md +++ b/source/blog/2015-10-14-rdo-test-day-summary.html.md @@ -7,7 +7,7 @@ comments: true published: true --- -A big thanks to everyone that participated in the [RDO Test Day](http://beta.rdoproject.org/testday/rdo-test-day-liberty-02/) over the last 48 hours. Here's a few statistics from the day. +A big thanks to everyone that participated in the [RDO Test Day](https://www.rdoproject.org/testday/) over the last 48 hours. Here's a few statistics from the day. 29 people wrote 74 email messages to the [rdo-list mailing list](https://www.redhat.com/archives/rdo-list/2015-October/thread.html). (Of course, they weren't all about the test day, but many of them were.) @@ -15,6 +15,6 @@ A big thanks to everyone that participated in the [RDO Test Day](http://beta.rdo We had [23 new issues](http://tm3.org/liberty-test-day-bugs) opened in the ticketing system. -Some people have put their day's experience in the [etherpad](https://etherpad.openstack.org/p/rdo_test_day_oct_2015) and some have updated the [Tested Scenarios page](http://beta.rdoproject.org/testday/testedsetups-liberty-02/). If you didn't put your notes anywhere, please do update one of those in the coming day or two, so that we don't lose what we learned. +Some people have put their day's experience in the [etherpad](https://etherpad.openstack.org/p/rdo_test_day_oct_2015). If you didn't put your notes anywhere, please do update the etherpad in the coming day or two, so that we don't lose what we learned. So, thanks to all of you. Particular thanks to trown for getting things rolling and herding the cats. diff --git a/source/blog/2015-10-22-rdo-liberty-released-in-centos-cloud-sig.html.md b/source/blog/2015-10-22-rdo-liberty-released-in-centos-cloud-sig.html.md index 98e450335..a48763d73 100644 --- a/source/blog/2015-10-22-rdo-liberty-released-in-centos-cloud-sig.html.md +++ b/source/blog/2015-10-22-rdo-liberty-released-in-centos-cloud-sig.html.md @@ -21,7 +21,7 @@ own onpremise, public or hybrid clouds. In addition to the comprehensive OpenStack services, libraries and clients, this release also provides Packstack, a simple installer for proof-of-concept installations, as small as a single all-in-one box and -[RDO Manager](https://www.rdoproject.org/RDO-Manager), an OpenStack +[TripleO](/tripleo), an OpenStack deployment and management tool for production environments based on the OpenStack TripleO project. @@ -33,10 +33,9 @@ Ensure you have a fully updated CentOS Linux 7/x86\_64 machine, and run : sudo yum install openstack-packstack packstack --allinone -For a more detailed quickstart please refer to the [RDO Project hosted -guide](https://www.rdoproject.org/QuickStart). +For a more detailed quickstart please refer to the [RDO Project hosted guide](/install). -For RDO Manager consult the [RDO Manager page](https://www.rdoproject.org/RDO-Manager). +For TripleO consult the [TripleO Quickstart page](/tripleo). RDO project is closely tracking upstream OpenStack projects using the [Delorean tool](http://trunk.rdoproject.org/) which is producing RPM packages from upstream development branches. diff --git a/source/blog/2016-02-23-rdo-mitaka-3-test-day-march-10th-11th.html.md b/source/blog/2016-02-23-rdo-mitaka-3-test-day-march-10th-11th.html.md index cd2eacaef..f9e62b7fd 100644 --- a/source/blog/2016-02-23-rdo-mitaka-3-test-day-march-10th-11th.html.md +++ b/source/blog/2016-02-23-rdo-mitaka-3-test-day-march-10th-11th.html.md @@ -13,14 +13,14 @@ TL;DR: * [On-site test day in Brno](https://www.rdoproject.org/testday/mitaka/brno-on-site/) * [Demo of deploying with TripleO](https://www.youtube.com/watch?v=4O8KvC66eeU) -[Mitaka milestone 3](http://releases.openstack.org/mitaka/schedule.html) is scheduled for the week of February 29 - March 4 and, as per usual, we're planning a test day about a week out from that - March 10th and 11th. We've got the usual [page of instructions](https://www.rdoproject.org/testday/mitaka/milestone3/) for testing. +[Mitaka milestone 3](http://releases.openstack.org/mitaka/schedule.html) is scheduled for the week of February 29 - March 4 and, as per usual, we're planning a test day about a week out from that - March 10th and 11th. We've got the usual [page of instructions](https://www.rdoproject.org/testday/) for testing. This time, however, we have two bonus events. -First, we're delighted that Eliska Malikova is putting together an [on-site test day at the Red Hat office in Brno](https://www.rdoproject.org/testday/mitaka/brno-on-site/), for anyone in that general area. If you wish to attend, [please register](https://www.eventbrite.com/e/rdo-on-site-test-day-brno-tickets-5934822213) so that we know how much pizza to order. (Attendance is limited to 50, so please register sooner rather than later.) +First, we're delighted that Eliska Malikova is putting together an [on-site test day at the Red Hat office in Brno](/testday), for anyone in that general area. If you wish to attend, [please register](https://www.eventbrite.com/e/rdo-on-site-test-day-brno-tickets-5934822213) so that we know how much pizza to order. (Attendance is limited to 50, so please register sooner rather than later.) Second, as we attempt to get more people testing TripleO (formerly known as RDO Manager), John Trownbridge (that's Trown on IRC) will be doing a demo of the TripleO Quickstart. This will be conducted as a [YouTube live stream](https://www.youtube.com/watch?v=4O8KvC66eeU) and will also be recorded, and available at that same location after the fact. -So, please, come help us ensure that Mitaka is the best RDO yet. As usual, we'll be on #rdo (on Freenode IRC), and here on rdo-list, to field any questions. Full details are on the [test day website](https://www.rdoproject.org/testday/mitaka/milestone3/) and, as usual, we can use lots of help making the test case instructions better, so that more people can participate. +So, please, come help us ensure that Mitaka is the best RDO yet. As usual, we'll be on #rdo (on Freenode IRC), and here on rdo-list, to field any questions. Full details are on the [test day website](/testday/) and, as usual, we can use lots of help making the test case instructions better, so that more people can participate. Thanks! diff --git a/source/blog/2016-04-06-upcoming-events-in-openstack-and-rdo.html.md b/source/blog/2016-04-06-upcoming-events-in-openstack-and-rdo.html.md index 64d8b82fc..230f43558 100644 --- a/source/blog/2016-04-06-upcoming-events-in-openstack-and-rdo.html.md +++ b/source/blog/2016-04-06-upcoming-events-in-openstack-and-rdo.html.md @@ -13,11 +13,10 @@ There's also a huge surge in things to announce around the RDO community, as we * The [upstream release of Mitaka](http://releases.openstack.org/mitaka/schedule.html) is this week. [Stackalytics](http://stackalytics.com/?metric=commits) lists over 2500 people who have contributed to this release. -* We'll be conducting a [test day for RDO Mitaka on April 13th and 14th](https://www.rdoproject.org/testday/mitaka/ga/). +* We'll be conducting a [test day for RDO Mitaka on April 13th and 14th](https://www.rdoproject.org/testday/). * [OpenStack Summit](http://openstack.org/summit) is just 2 weeks away, and we'll be having an [RDO BoF](https://www.openstack.org/summit/austin-2016/summit-schedule/events/6892) (Birds of a Feather) gathering there. * If you have something you'd like to demo in the RDO booth at OpenStack Summit, add your idea to the [booth schedule etherpad](https://etherpad.openstack.org/p/rdo-austin-summit-booth). And, as every week, there are lots of [OpenStack Meetups](http://rdoproject.org/events/) all over the world this week. Especially don't miss Perry Meyers' RDO Q&A at the [Morgantown OpenStack Meetup](http://www.meetup.com/Morgantown-Linux-User-Group/events/227482742/). - diff --git a/source/blog/2016-04-12-newbie-in-rdo-2-rdo-trunk-from-a-bird-s-eye-view.html.md b/source/blog/2016-04-12-newbie-in-rdo-2-rdo-trunk-from-a-bird-s-eye-view.html.md index 36855c6e5..55244e39d 100644 --- a/source/blog/2016-04-12-newbie-in-rdo-2-rdo-trunk-from-a-bird-s-eye-view.html.md +++ b/source/blog/2016-04-12-newbie-in-rdo-2-rdo-trunk-from-a-bird-s-eye-view.html.md @@ -6,7 +6,7 @@ date: 2016-04-12 18:45:18 CEST published: true --- -Time goes fast as a RDO newbie and once I understood what the RDO Trunk and CloudSIG repos provide (read my [previous post](https://www.rdoproject.org/blog/2016/05/new-in-rdo-repos-one-size-doesn-t-fit-all/) if you still have doubts), my next goal was to have a clear high-level perspective of the entire delivery workflow followed in the project. +Time goes fast as a RDO newbie and once I understood what the RDO Trunk and CloudSIG repos provide (read my [previous post](https://www.rdoproject.org/blog/2016/04/new-in-rdo-repos-one-size-doesn-t-fit-all/) if you still have doubts), my next goal was to have a clear high-level perspective of the entire delivery workflow followed in the project. Although there is a lot of detailed and great information in different sources (see [More info](####More info) at the end of the post), it may be useful for others to provide a high level and global description of it. In this post I'll focus in the process around RDO Trunk repositories as shown in the following diagram: diff --git a/source/blog/2016-04-12-rdo-mitaka-released.html.md b/source/blog/2016-04-12-rdo-mitaka-released.html.md index 49816e8d3..2ecb7e0d7 100644 --- a/source/blog/2016-04-12-rdo-mitaka-released.html.md +++ b/source/blog/2016-04-12-rdo-mitaka-released.html.md @@ -7,14 +7,14 @@ comments: true published: true --- -The RDO community is pleased to announce the general availability of the RDO build for OpenStack Mitaka for RPM-based distributions - CentOS Linux 7 and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds and Mitaka is the 13th release from the [OpenStack project](http://openstack.org), which is the work of more than 2500 contributors from around the world. +The RDO community is pleased to announce the general availability of the RDO build for OpenStack Mitaka for RPM-based distributions - CentOS Linux 7 and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds and Mitaka is the 13th release from the [OpenStack project](http://openstack.org), which is the work of more than 2500 contributors from around the world. ([Source](http://stackalytics.com/)) See [RedHatStack](http://redhatstackblog.redhat.com/2016/03/21/learn-whats-coming-in-openstack-mitaka/) for a brief overview of what's new in Mitaka. The [RDO community project](https://www.rdoproject.org/) curates, packages, builds, tests, and maintains a complete OpenStack component set for RHEL and CentOS Linux and is a founding member of the [CentOS Cloud Infrastructure SIG](https://wiki.centos.org/SpecialInterestGroup/Cloud). The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS Linux users looking to build and maintain their own on-premise, public or hybrid clouds. -All work on RDO, and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. +All work on RDO, and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. For a complete list of what's in RDO, see [the RDO projects yaml file](https://github.com/redhat-openstack/rdoinfo/blob/master/rdo.yml). @@ -22,7 +22,7 @@ For a complete list of what's in RDO, see [the RDO projects yaml file](https://g There are three ways to get started with RDO. -To spin up a proof of concept cloud, quickly, and on limited hardware, try the [RDO QuickStart](http://rdoproject.org/Quickstart) You can run RDO on a single node to get a feel for how it works. +To spin up a proof of concept cloud, quickly, and on limited hardware, try [Packstack](https://www.rdoproject.org/install/packstack/). You can run RDO on a single node to get a feel for how it works. For a production deployment of RDO, use the [TripleO Quickstart](https://www.rdoproject.org/tripleo/) and you'll be running a production cloud in short order. @@ -30,7 +30,7 @@ Finally, if you want to try out OpenStack, but don't have the time or hardware t **Getting Help** - + The RDO Project participates in a Q&A service at [ask.openstack.org](http://ask.openstack.org), for more developer oriented content we recommend joining the [rdo-list mailing list](https://www.redhat.com/mailman/listinfo/rdo-list). Remember to post a brief introduction about yourself and your RDO story. You can also find extensive documentation on the [RDO docs site](https://www.rdoproject.org/documentation). We also welcome comments and requests on the [CentOS Mailing lists](https://lists.centos.org/) and the CentOS IRC Channels (#centos on irc.freenode.net), however we have a more focused audience in the RDO venues. @@ -42,4 +42,4 @@ To get involved in the OpenStack RPM packaging effort, see the [RDO community pa Join us in #rdo on the Freenode IRC network, and follow us at [@RDOCommunity](http://twitter.com/rdocommunity) on Twitter. -And, if you're going to be in Austin for the [OpenStack Summit](http://openstack.org/summit/) two weeks from now, join us on Thursday at 4:40pm for the [RDO community BoF](https://goo.gl/P6kyWR). \ No newline at end of file +And, if you're going to be in Austin for the [OpenStack Summit](http://openstack.org/summit/) two weeks from now, join us on Thursday at 4:40pm for the [RDO community BoF](https://goo.gl/P6kyWR). diff --git a/source/blog/2016-05-03-announcement-migration-to-reviewrdoprojectorg.html.md b/source/blog/2016-05-03-announcement-migration-to-reviewrdoprojectorg.html.md index 81200b2e6..1d7d7fe5a 100644 --- a/source/blog/2016-05-03-announcement-migration-to-reviewrdoprojectorg.html.md +++ b/source/blog/2016-05-03-announcement-migration-to-reviewrdoprojectorg.html.md @@ -7,7 +7,7 @@ published: true --- After releasing RDO Mitaka, we migrated our current packaging workflow from gerrithub to a brand-new platform hosted at [https://review.rdoproject.org](https://review.rdoproject.org) right before the Newton Summit. -During the last cycle, we've worked with [Software Factory](https://software-factory.io) folks to build a new packaging workflow based on the very same foundations as upstream OpenStack (using gerrit, zuul, nodepool). We're now relying on RPMFactory which is a specialization of Software Factory fitted for RPM packaging needs. +During the last cycle, we've worked with [Software Factory](https://softwarefactory-project.io) folks to build a new packaging workflow based on the very same foundations as upstream OpenStack (using gerrit, zuul, nodepool). We're now relying on RPMFactory which is a specialization of Software Factory fitted for RPM packaging needs. The migration was planned in order to satisfy some criteria: diff --git a/source/blog/2016-06-08-june-rdo-newsletter.html.md b/source/blog/2016-06-08-june-rdo-newsletter.html.md index 64ba79486..1be16b8ce 100644 --- a/source/blog/2016-06-08-june-rdo-newsletter.html.md +++ b/source/blog/2016-06-08-june-rdo-newsletter.html.md @@ -11,6 +11,6 @@ published: true
-In case you missed it, the June RDO newsletter is [now available](https://www.rdoproject.org/newsletter/2016-june/). +In case you missed it, the June RDO newsletter is [now available](/newsletter/2016/june/). -If you're not receiving the RDO newsletter, you can subscribe by sending email to [rdo-newsletter-subscribe@redhat.com](mailto:rdo-newsletter-subscribe@redhat.com). The newsletter is sent the first week of every month, and covers what's been going on in the RDO community, and what's happening in the coming weeks. +If you're not receiving the RDO newsletter, you can subscribe at [https://www.redhat.com/mailman/listinfo/rdo-newsletter](mhttps://www.redhat.com/mailman/listinfo/rdo-newsletter). The newsletter is sent the first week of every month, and covers what's been going on in the RDO community, and what's happening in the coming weeks. diff --git a/source/blog/2016-06-20-openstack-days-budapest-openstack-days-prague.html.md b/source/blog/2016-06-20-openstack-days-budapest-openstack-days-prague.html.md index c75e1ccb6..b06a2ec05 100644 --- a/source/blog/2016-06-20-openstack-days-budapest-openstack-days-prague.html.md +++ b/source/blog/2016-06-20-openstack-days-budapest-openstack-days-prague.html.md @@ -14,19 +14,18 @@ published: true It was the [4th OSD in Budapest](http://openstackceeday.com/), but at a brand new place, which was absolutely brilliant. And by brilliant I mean - nice place to stay, great location, enough options around, very good sound, well working AC in rooms for talks and professional catering. I am not sure about number of attendees, but it was pretty big and crowded - so awesome! I really can say that it was awesome experience for me (please accept my apology for using word “awesome” too often here). I brought 2 banners - [RDO](http://rdoproject.org) + OpenStack, RDO stickers, TripleO stickers with the Owl, RDO/CentOS beermats, cheat-sheets, leaflets and few t-shirts. It was only RH booth at the beginning, but I changed it a bit into RDO by adding those promo stuff. It was distributed very well. The problem of this OSD is (and I was warned in advance by Ondrej Marek) that there are mostly Hungarian people, who are not very open to have some discussion or ask many questions. I was at a booth between talks anyway. Also I joined many talks, had a nice discussion with Marketing guys on the booth and meet also one RH Sales guy Miroslaw Pawlowski (from PL). -It was very nice, very well organised OSD. Lovely food, lovely place, great people, nice talks, it was a bit more quiet than on FOSDEM or Devconf.cz. But that is probably something related to the nationality, as Ondrej mentioned. +It was very nice, very well organised OSD. Lovely food, lovely place, great people, nice talks, it was a bit more quiet than on FOSDEM or Devconf.cz. But that is probably something related to the nationality, as Ondrej mentioned. -Hugh Brock from our team had a great [TripleO](http://rdoproject.org/tripleo/) talk, received some questions after a talk. It was very nice talk with cool jokes. +Hugh Brock from our team had a great [TripleO](http://rdoproject.org/tripleo/) talk, received some questions after a talk. It was very nice talk with cool jokes. ## OpenStack Day - Prague, 8th June 2016 -This event was [1st OpenStack Day in Prague](http://openstackdayprague.eu). According to that I was really surprised how well organised and placed it was. For this event we were at DOX gallery, which is very modern, beautiful and quiet and also at a perfect distance from bus station. So we had a lot of space to go around, have a coffee, conversation or a good meal. At the entrance some OpenStack swag was distributed - OS sticker, super cool OpenStack glasses, some info leaflets and map of the area, also awesome bag saying “OpenStack Prague” which I now use for shopping and feel so cool now. Attendance was pretty large, we really filled that area with attendees. I meet there Zdenka Van Der Zwan and Ondrej Marek, that was just great to meet them in person. Also many people which I met in Budapest. I provided to Ondrej the info about OSD in Budapest and also we had a chance to discuss the swag, or what could I do to motivate people to attend a bit more, and also we agreed to be in touch to see in advance some more possibilities for future events. +This event was the 1st OpenStack Day in Prague. According to that I was really surprised how well organised and placed it was. For this event we were at DOX gallery, which is very modern, beautiful and quiet and also at a perfect distance from bus station. So we had a lot of space to go around, have a coffee, conversation or a good meal. At the entrance some OpenStack swag was distributed - OS sticker, super cool OpenStack glasses, some info leaflets and map of the area, also awesome bag saying “OpenStack Prague” which I now use for shopping and feel so cool now. Attendance was pretty large, we really filled that area with attendees. I meet there Zdenka Van Der Zwan and Ondrej Marek, that was just great to meet them in person. Also many people which I met in Budapest. I provided to Ondrej the info about OSD in Budapest and also we had a chance to discuss the swag, or what could I do to motivate people to attend a bit more, and also we agreed to be in touch to see in advance some more possibilities for future events. -I met also Jirka Kolář from TCP Cloud and also Aleš from Elostech and few other guys I know from local community. Ondrej confirmed that the community meetups are a bit silent, still but again - let's see how it will go. +I met also Jirka Kolář from TCP Cloud and also Aleš from Elostech and few other guys I know from local community. Ondrej confirmed that the community meetups are a bit silent, still but again - let's see how it will go. -We had there a beautiful Red Hat booth, with fancy RH promo stuff - free to take. Also you could win a quadricopter (if you were not a RH employee of course) by filling up a survey. I brought some RDO things, to refresh the RH booth. I took RDO banner, OpenStack banner, RDO stickers, beermats (super successful), cheat-sheets, TripleO stickers. I have great muscles now :D thanks to carrying heavy backpack and two banners, lol. +We had there a beautiful Red Hat booth, with fancy RH promo stuff - free to take. Also you could win a quadricopter (if you were not a RH employee of course) by filling up a survey. I brought some RDO things, to refresh the RH booth. I took RDO banner, OpenStack banner, RDO stickers, beermats (super successful), cheat-sheets, TripleO stickers. I have great muscles now :D thanks to carrying heavy backpack and two banners, lol. -Angus Thomas had a talk (the same that Hugh Brock had in Budapest OpenStack day) and we also had a chance to chat a bit and enjoy a lunch together. It was very nice. Hugh couldn't attend this OSD due to Dublin management meeting. It is a shame that not many people from our team were present at this Day. I met some technical writers (Radek Bíba, and his colleague whose name I forgot), Angus, few guys from Marketing. There was no one from HR - Tyler Golden couldn't attend. I met many familiar faces from Budapest there, but from our teams there was only me and Angus and Flavio Percoco, who traveled from Italy. I hope that next year there will be more attendance from our local team members. - -For a next OSD in Praha, I will advertise it much better. My vision is to travel there as a team and maybe have some nice dinner together? Let's see. But for a next time I would definitely ask people directly myself. +Angus Thomas had a talk (the same that Hugh Brock had in Budapest OpenStack day) and we also had a chance to chat a bit and enjoy a lunch together. It was very nice. Hugh couldn't attend this OSD due to Dublin management meeting. It is a shame that not many people from our team were present at this Day. I met some technical writers (Radek Bíba, and his colleague whose name I forgot), Angus, few guys from Marketing. There was no one from HR - Tyler Golden couldn't attend. I met many familiar faces from Budapest there, but from our teams there was only me and Angus and Flavio Percoco, who traveled from Italy. I hope that next year there will be more attendance from our local team members. +For a next OSD in Praha, I will advertise it much better. My vision is to travel there as a team and maybe have some nice dinner together? Let's see. But for a next time I would definitely ask people directly myself. diff --git a/source/blog/2016-10-04-rdo-newton-released.html.md b/source/blog/2016-10-04-rdo-newton-released.html.md index 1d57b535f..b29be63c8 100644 --- a/source/blog/2016-10-04-rdo-newton-released.html.md +++ b/source/blog/2016-10-04-rdo-newton-released.html.md @@ -10,14 +10,14 @@ The RDO community is pleased to announce the general availability of the RDO bui The [RDO community project](https://www.rdoproject.org/) curates, packages, builds, tests, and maintains a complete OpenStack component set for RHEL and CentOS Linux and is a member of the [CentOS Cloud Infrastructure SIG](https://wiki.centos.org/SpecialInterestGroup/Cloud). The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS Linux users looking to build and maintain their own on-premise, public or hybrid clouds. At latest count, RDO contains [1157 packages](https://www.rdoproject.org/documentation/package-list/). -All work on RDO, and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. +All work on RDO, and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. **Getting Started** There are three ways to get started with RDO. -To spin up a proof of concept cloud, quickly, and on limited hardware, try the [All-In-One Quickstart](http://rdoproject.org/Quickstart). You can run RDO on a single node to get a feel for how it works. +To spin up a proof of concept cloud, quickly, and on limited hardware, try [Packstack](https://www.rdoproject.org/install/packstack/). You can run RDO on a single node to get a feel for how it works. For a production deployment of RDO, use the [TripleO Quickstart](https://www.rdoproject.org/tripleo/) and you'll be running a production cloud in short order. @@ -25,7 +25,7 @@ Finally, if you want to try out OpenStack, but don't have the time or hardware t **Getting Help** - + The RDO Project participates in a Q&A service at [ask.openstack.org](http://ask.openstack.org), for more developer-oriented content we recommend joining the [rdo-list mailing list](https://www.redhat.com/mailman/listinfo/rdo-list). Remember to post a brief introduction about yourself and your RDO story. You can also find extensive documentation on the RDO docs sites [Documnentation](https://www.rdoproject.org/documentation/), [FAQS](https://www.rdoproject.org/rdo/faq/), [Contribute](https://www.rdoproject.org/contribute/), [Storage](https://www.rdoproject.org/storage/), [Books](https://www.rdoproject.org/documentation/books/), [Networking](https://www.rdoproject.org/networking/), [Install](https://www.rdoproject.org/install/). The #rdo channel on Freenode IRC is also an excellent place to find help and give help. diff --git a/source/blog/2016-10-05-how-to-run-rally-on-packstack.html.md b/source/blog/2016-10-05-how-to-run-rally-on-packstack.html.md index 84357790d..6c649dacc 100644 --- a/source/blog/2016-10-05-how-to-run-rally-on-packstack.html.md +++ b/source/blog/2016-10-05-how-to-run-rally-on-packstack.html.md @@ -5,7 +5,7 @@ tags: rally, packstack, tempest, bechmarking date: 2016-10-05 10:10:15 UTC --- -[Rally](https://rally.readthedocs.io/en/latest/overview.html) is a benchmarking tool that automates and unifies multi-node OpenStack deployment, cloud verification, benchmarking & profiling. +[Rally](https://rally.readthedocs.io) is a benchmarking tool that automates and unifies multi-node OpenStack deployment, cloud verification, benchmarking & profiling. For OpenStack deployment I used [packstack](https://www.rdoproject.org/install/packstack/) tool. ## Install Rally diff --git a/source/blog/2016-11-22-chasing-the-trunk-but-not-too-fast.html.md b/source/blog/2016-11-22-chasing-the-trunk-but-not-too-fast.html.md index d6fa72a71..7d3891ea3 100644 --- a/source/blog/2016-11-22-chasing-the-trunk-but-not-too-fast.html.md +++ b/source/blog/2016-11-22-chasing-the-trunk-but-not-too-fast.html.md @@ -5,7 +5,7 @@ tags: date: 2016-11-22 10:10:08 CET --- -As explained in [a previous post](https://www.rdoproject.org/blog/2016/05/new-in-rdo-repos-one-size-doesn-t-fit-all/), +As explained in [a previous post](https://www.rdoproject.org/blog/2016/04/new-in-rdo-repos-one-size-doesn-t-fit-all/), in RDO Trunk repositories we try to provide packages for new commits in OpenStack projects as soon as possible after they are merged upstream. This has a number of advantages: diff --git a/source/blog/2017-03-16-rdo-ci-in-a-nutshell.html.md b/source/blog/2017-03-16-rdo-ci-in-a-nutshell.html.md index ec20c6c69..3e6314c67 100644 --- a/source/blog/2017-03-16-rdo-ci-in-a-nutshell.html.md +++ b/source/blog/2017-03-16-rdo-ci-in-a-nutshell.html.md @@ -127,5 +127,5 @@ status of RDO packaging and CI. * [TripleO quickstart demostration](https://www.youtube.com/watch?v=4O8KvC66eeU) by trown * [Weirdo: A talk about CI in OpenStack and RDO](https://dmsimard.com/2016/03/02/openstack-montreal-a-talk-about-ci-in-openstack-and-rdo/) by dmsimard. -* [ARA blog posts](https://dmsimard.com/tag/ara.html) - from dmsimard blog +* [ARA blog posts](https://dmsimard.com/categories/ara) - from dmsimard blog * [Ci in RDO: What do we test?](https://amoralej.fedorapeople.org/slides/RDO-CI-summit-bcn-final.pdf) - presentation in RDO and Ceph Meetup BCN. diff --git a/source/blog/2017-05-08-running-and-recording-fully-automated-GUI-tests-in-the-cloud.html.md b/source/blog/2017-05-08-running-and-recording-fully-automated-GUI-tests-in-the-cloud.html.md index 93ce4685d..d172e3b02 100644 --- a/source/blog/2017-05-08-running-and-recording-fully-automated-GUI-tests-in-the-cloud.html.md +++ b/source/blog/2017-05-08-running-and-recording-fully-automated-GUI-tests-in-the-cloud.html.md @@ -13,7 +13,7 @@ CI/CD pipelines. It is the engine behind [RDO's CI pipeline](https://review.rdop but it is also very versatile and suited for all kinds of software projects. Also, I happen to be one of Software Factory's main contributors. :) -Software Factory has [many cool features that I won't list here](https://softwarefactory-project.io/docs/intro.html), but among these +Software Factory has [many cool features that I won't list here](https://softwarefactory-project.io/docs/index.html), but among these is a unified web interface that helps navigating through its components. Obviously we want this interface thoroughly tested; ideally within Software Factory's own CI system, which runs on test nodes being provisioned on demand on an OpenStack @@ -73,7 +73,8 @@ the dependencies we need: sudo yum install -y firefox Xvfb libXfont Xorg jre sudo mkdir /usr/lib/selenium /var/log/selenium /var/log/Xvfb sudo wget -O /usr/lib/selenium/selenium-server.jar http://selenium-release.storage.googleapis.com/3.4/selenium-server-standalone-3.4.0.jar -sudo pip install selenium``` +sudo pip install selenium +``` The dependencies are: @@ -88,13 +89,15 @@ in the background: ```bash /usr/bin/java -jar /usr/lib/selenium/selenium-server.jar -host 127.0.0.1 >/var/log/selenium/selenium.log 2>/var/log/selenium/error.log -Xvfb :99 -ac -screen 0 1920x1080x24 >/var/log/Xvfb/Xvfb.log 2>/var/log/Xvfb/error.log``` +Xvfb :99 -ac -screen 0 1920x1080x24 >/var/log/Xvfb/Xvfb.log 2>/var/log/Xvfb/error.log +``` Finally, set the display environment variable to :99 (the Xvfb display) and run your tests: ```bash export DISPLAY=:99 -./path/to/seleniumtests``` +./path/to/seleniumtests +``` The tests will run as if the VM was plugged to a display. @@ -166,7 +169,8 @@ sudo yum install -y ffmpeg To record the Xfvb buffer, you'd simply run ```bash -export FFREPORT=file=/tmp/gui/ffmpeg-$(date +%Y%m%s).log && ffmpeg -f x11grab -video_size 1920x1080 -i 127.0.0.1$DISPLAY -codec:v mpeg4 -r 16 -vtag xvid -q:v 8 /tmp/gui/tests.avi ``` +export FFREPORT=file=/tmp/gui/ffmpeg-$(date +%Y%m%s).log && ffmpeg -f x11grab -video_size 1920x1080 -i 127.0.0.1$DISPLAY -codec:v mpeg4 -r 16 -vtag xvid -q:v 8 /tmp/gui/tests.avi +``` The catch is that ffmpeg expects the user to press __q__ to stop the recording and save the video (killing the process will corrupt the video). We can use diff --git a/source/blog/2017-08-01-rdopkg-0.44-changeblog.html.md b/source/blog/2017-08-01-rdopkg-0.44-changeblog.html.md index 3c1c89613..6e0f06be1 100644 --- a/source/blog/2017-08-01-rdopkg-0.44-changeblog.html.md +++ b/source/blog/2017-08-01-rdopkg-0.44-changeblog.html.md @@ -17,7 +17,9 @@ with a blog post about the changes - a **ChangeBlog** ;) **41 commits** from **7 contributors** were merged over the course of **4 months** since last release with average **time to land of 6 days**. + For more information about each change, follow the link to inspect related commit on github. @@ -26,7 +28,7 @@ commit on github. ## Software Factory migration ### [Migrate to softwarefactory-project.io](https://github.com/softwarefactory-project/rdopkg/commit/f76bbd6) -* `rdopkg` now has a +* `rdopkg` now has a [new home under software factory project](https://softwarefactory-project.io/repoxplorer/project.html?pid=rdopkg) alongside [DLRN](https://softwarefactory-project.io/repoxplorer/project.html?pid=DLRN). * Github repository also @@ -66,7 +68,7 @@ using Then .spec file has 3 patches defined Then .spec file contains new changelog entry with 1 lines Then new commit was created - + It also looks reasonable on the [pyton side](https://github.com/softwarefactory-project/rdopkg/blob/master/features/steps/distgit.py). ### [Avoid test failure due to git hooks](https://github.com/softwarefactory-project/rdopkg/commit/6a7798a) diff --git a/source/blog/2017-09-26-openstack-3rd-party-ci-with-software-factory.html.md b/source/blog/2017-09-26-openstack-3rd-party-ci-with-software-factory.html.md index 3e4b1cfd9..167402ea7 100644 --- a/source/blog/2017-09-26-openstack-3rd-party-ci-with-software-factory.html.md +++ b/source/blog/2017-09-26-openstack-3rd-party-ci-with-software-factory.html.md @@ -1,7 +1,7 @@ --- title: OpenStack 3rd Party CI with Software Factory author: jpena -tags: +tags: date: 2017-09-26 11:34:30 CEST --- @@ -143,7 +143,7 @@ nodepool: - The authentication options if you want other users to be able to log into your instance of Software Factory using OAuth providers like GitHub. This is not mandatory for a 3rd party CI. -See [this part of the documentation](https://softwarefactory-project.io/docs/auths.html#oauth2-based-authentication) for details. +See [this part of the documentation](https://softwarefactory-project.io/docs/operator/auths.html) for details. - If you want to use [LetsEncrypt](https://letsencrypt.org/) to get a proper SSL certificate, set: @@ -316,7 +316,7 @@ image we just created in Nodepool. $ vi zuul/upstream.yaml ``` -We are creating a specific [Zuul pipeline](https://docs.openstack.org/infra/zuul/zuul.html#pipelines) +We are creating a specific [Zuul pipeline](https://docs.openstack.org/infra/zuul/user/concepts.html) for changes coming from the OpenStack Gerrit, and specifying that we want to run a CI job for commits to the ci-sandbox project: From abd612d2a38abbda6d7101f7429a6473bf7139c6 Mon Sep 17 00:00:00 2001 From: Mary Thengvall Date: Tue, 16 Jan 2018 23:03:48 -0800 Subject: [PATCH 4/9] fixed image name and location --- ...aring_ip.png => Neutron_private_floating_ip.png} | Bin 1 file changed, 0 insertions(+), 0 deletions(-) rename source/images/{wiki/Neutron_private_floaring_ip.png => Neutron_private_floating_ip.png} (100%) diff --git a/source/images/wiki/Neutron_private_floaring_ip.png b/source/images/Neutron_private_floating_ip.png similarity index 100% rename from source/images/wiki/Neutron_private_floaring_ip.png rename to source/images/Neutron_private_floating_ip.png From 7d2664aac747053d3afcc28d586716234f7e2f3c Mon Sep 17 00:00:00 2001 From: Mary Thengvall Date: Tue, 16 Jan 2018 23:04:16 -0800 Subject: [PATCH 5/9] fixed testday links --- source/testday/pike/workarounds1.html.md | 7 +++---- source/testday/queens/milestone1.html.md | 8 ++++---- source/testday/queens/milestone2.html.md | 10 +++++----- source/testday/queens/milestone3.html.md | 10 +++++----- source/testday/tests/index.html.md | 18 ++++++++++-------- 5 files changed, 27 insertions(+), 26 deletions(-) diff --git a/source/testday/pike/workarounds1.html.md b/source/testday/pike/workarounds1.html.md index 0196e5103..05a15c7bf 100644 --- a/source/testday/pike/workarounds1.html.md +++ b/source/testday/pike/workarounds1.html.md @@ -1,17 +1,16 @@ --- -title: RDO Ocata Test Day Workarounds +title: RDO Pike Test Day Workarounds --- -# Workarounds, Ocata Test Day 1 +# Workarounds, Pike Test Day 1 If you discover a way to work around a known problem, please document it here, so that others may benefit from your experience. -[Test Day Details](/testday/ocata/milestone1) +[Test Day Details](/testday/pike/milestone1) ## All ## TripleO ## Packstack - diff --git a/source/testday/queens/milestone1.html.md b/source/testday/queens/milestone1.html.md index aba0caba0..73b229793 100644 --- a/source/testday/queens/milestone1.html.md +++ b/source/testday/queens/milestone1.html.md @@ -19,7 +19,7 @@ We will also be available for people that want to try the stable (Pike) release. ### Quick links * [Test matrix](/testday/tests) -* [Workarounds](/testday/queens/workarounds1) +* [Workarounds](https://etherpad.openstack.org/p/rdo-test-days-queens1-workarounds) ## Prerequisites @@ -43,7 +43,7 @@ You'll want a fresh install with latest updates installed. ### Next steps -* Check for any [workarounds](/testday/queens/workarounds1) required for your platform before the main installation. +* Check for any [workarounds](https://etherpad.openstack.org/p/rdo-test-days-queens1-workarounds) required for your platform before the main installation. * For a TripleO-based installation, try the [TripleO quickstart](https://www.rdoproject.org/tripleo/). @@ -54,7 +54,7 @@ You'll want a fresh install with latest updates installed. The scenarios that should be tested are listed on the [test matrix](/testday/tests) page. This will be copied to an etherpad the day of the test, for easier annotation during the event. 1. Pick an item from the list. -1. Go through the scenario as though you were a beginner, just following the instructions. (Check the [workarounds](/testday/queens/workarounds1) page for problems that others may have encountered and resolved.) +1. Go through the scenario as though you were a beginner, just following the instructions. (Check the [workarounds](https://etherpad.openstack.org/p/rdo-test-days-queens1-workarounds) page for problems that others may have encountered and resolved.) 1. **Keep good notes.** You can use [the test day etherpad](https://etherpad.openstack.org/p/rdo-test-days-queens-m1) for these notes. Reviewing other peoples' notes may help you avoid problems that they've already encountered. If you have problems with any of the tests, report a bug to [Bugzilla](https://bugzilla.redhat.com) usually for one of the @@ -62,4 +62,4 @@ If you have problems with any of the tests, report a bug to [Bugzilla](https://b [openstack-nova](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-nova), [openstack-glance](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-glance), [openstack-keystone](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-keystone), [openstack-cinder](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-cinder), [openstack-neutron](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-neutron), [openstack-swift](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-swift), [python-django-horizon](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=python-django-horizon), [openstack-heat](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-heat) or [openstack-ceilometer](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-ceilometer) components. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC (#rdo, freenode.net) and we will help you. -Once you have completed the tests, add your results to the table on the [test matrix](/testday/tests) page, following the examples already there. Be sure to check the [workarounds](/testday/queens/workarounds1) page for things that may have already have fixes or workarounds. +Once you have completed the tests, add your results to the table on the [test matrix](/testday/tests) page, following the examples already there. Be sure to check the [workarounds](https://etherpad.openstack.org/p/rdo-test-days-queens1-workarounds) page for things that may have already have fixes or workarounds. diff --git a/source/testday/queens/milestone2.html.md b/source/testday/queens/milestone2.html.md index 7cf6930fd..92739b6bb 100644 --- a/source/testday/queens/milestone2.html.md +++ b/source/testday/queens/milestone2.html.md @@ -22,7 +22,7 @@ etherpad](https://etherpad.openstack.org/p/rdo-queens-m2-cloud) ### Quick links * [Test matrix](/testday/tests) -* [Workarounds](/testday/queens/workarounds2) +* [Workarounds](https://etherpad.openstack.org/p/rdo-test-days-queens2-workarounds) ## Prerequisites @@ -36,7 +36,7 @@ You'll want a fresh install with latest updates installed. ## How to test? -There are two ways to test. +There are two ways to test. ### Test on our test cloud. @@ -60,7 +60,7 @@ own hardware: ### Next steps -* Check for any [workarounds](/testday/queens/workarounds2) required for your platform before the main installation. +* Check for any [workarounds](https://etherpad.openstack.org/p/rdo-test-days-queens2-workarounds) required for your platform before the main installation. * For a TripleO-based installation, try the [TripleO quickstart](https://www.rdoproject.org/tripleo/). @@ -71,7 +71,7 @@ own hardware: The scenarios that should be tested are listed on the [test matrix](/testday/tests) page. This will be copied to an etherpad the day of the test, for easier annotation during the event. 2. Pick an item from the list. -1. Go through the scenario as though you were a beginner, just following the instructions. (Check the [workarounds](/testday/queens/workarounds2) page for problems that others may have encountered and resolved.) +1. Go through the scenario as though you were a beginner, just following the instructions. (Check the [workarounds](https://etherpad.openstack.org/p/rdo-test-days-queens2-workarounds) page for problems that others may have encountered and resolved.) 1. **Keep good notes.** You can use [the test day etherpad](https://etherpad.openstack.org/p/rdo-test-days-queens-m2) for these notes. Reviewing other peoples' notes may help you avoid problems that they've already encountered. If you have problems with any of the tests, report a bug to [Bugzilla](https://bugzilla.redhat.com) usually for one of the @@ -79,4 +79,4 @@ If you have problems with any of the tests, report a bug to [Bugzilla](https://b [openstack-nova](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-nova), [openstack-glance](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-glance), [openstack-keystone](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-keystone), [openstack-cinder](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-cinder), [openstack-neutron](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-neutron), [openstack-swift](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-swift), [python-django-horizon](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=python-django-horizon), [openstack-heat](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-heat) or [openstack-ceilometer](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-ceilometer) components. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC (#rdo, freenode.net) and we will help you. -Once you have completed the tests, add your results to the table on the [test matrix](/testday/tests) page, following the examples already there. Be sure to check the [workarounds](/testday/queens/workarounds2) page for things that may have already have fixes or workarounds. +Once you have completed the tests, add your results to the table on the [test matrix](/testday/tests) page, following the examples already there. Be sure to check the [workarounds](https://etherpad.openstack.org/p/rdo-test-days-queens2-workarounds) page for things that may have already have fixes or workarounds. diff --git a/source/testday/queens/milestone3.html.md b/source/testday/queens/milestone3.html.md index a28ebee3b..dc234a334 100644 --- a/source/testday/queens/milestone3.html.md +++ b/source/testday/queens/milestone3.html.md @@ -22,7 +22,7 @@ etherpad](https://etherpad.openstack.org/p/rdo-queens-m3-cloud) ### Quick links * [Test matrix](/testday/tests) -* [Workarounds](/testday/queens/workarounds3) +* [Workarounds](https://etherpad.openstack.org/p/rdo-test-days-queens3-workarounds) ## Prerequisites @@ -36,7 +36,7 @@ You'll want a fresh install with latest updates installed. ## How to test? -There are two ways to test. +There are two ways to test. ### Test on our test cloud. @@ -60,7 +60,7 @@ own hardware: ### Next steps -* Check for any [workarounds](/testday/queens/workarounds3) required for your platform before the main installation. +* Check for any [workarounds](https://etherpad.openstack.org/p/rdo-test-days-queens3-workarounds) required for your platform before the main installation. * For a TripleO-based installation, try the [TripleO quickstart](https://www.rdoproject.org/tripleo/). @@ -71,7 +71,7 @@ own hardware: The scenarios that should be tested are listed on the [test matrix](/testday/tests) page. This will be copied to an etherpad the day of the test, for easier annotation during the event. 2. Pick an item from the list. -1. Go through the scenario as though you were a beginner, just following the instructions. (Check the [workarounds](/testday/queens/workarounds3) page for problems that others may have encountered and resolved.) +1. Go through the scenario as though you were a beginner, just following the instructions. (Check the [workarounds](https://etherpad.openstack.org/p/rdo-test-days-queens3-workarounds) page for problems that others may have encountered and resolved.) 1. **Keep good notes.** You can use [the test day etherpad](https://etherpad.openstack.org/p/rdo-test-days-queens-m3) for these notes. Reviewing other peoples' notes may help you avoid problems that they've already encountered. If you have problems with any of the tests, report a bug to [Bugzilla](https://bugzilla.redhat.com) usually for one of the @@ -79,4 +79,4 @@ If you have problems with any of the tests, report a bug to [Bugzilla](https://b [openstack-nova](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-nova), [openstack-glance](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-glance), [openstack-keystone](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-keystone), [openstack-cinder](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-cinder), [openstack-neutron](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-neutron), [openstack-swift](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-swift), [python-django-horizon](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=python-django-horizon), [openstack-heat](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-heat) or [openstack-ceilometer](https://bugzilla.redhat.com/enter_bug.cgi?product=RDO&component=openstack-ceilometer) components. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC (#rdo, freenode.net) and we will help you. -Once you have completed the tests, add your results to the table on the [test matrix](/testday/tests) page, following the examples already there. Be sure to check the [workarounds](/testday/queens/workarounds3) page for things that may have already have fixes or workarounds. +Once you have completed the tests, add your results to the table on the [test matrix](/testday/tests) page, following the examples already there. Be sure to check the [workarounds](https://etherpad.openstack.org/p/rdo-test-days-queens3-workarounds) page for things that may have already have fixes or workarounds. diff --git a/source/testday/tests/index.html.md b/source/testday/tests/index.html.md index bc0ac2d56..420e00ee9 100644 --- a/source/testday/tests/index.html.md +++ b/source/testday/tests/index.html.md @@ -5,7 +5,9 @@ Scenarios to test. If you test something that someone else has already made note Copy this outline to a public etherpad for each test day. Please update this template if tests are added or modified. + ## "Does it work" tests @@ -48,8 +50,8 @@ encouraged to perform some of the following test scenarios. ### Packstack 3 node * CentOS 7 * Instructions: https://www.rdoproject.org/testday/newton/final/#how-to-test -* Who: -* Results: +* Who: +* Results: * Tickets: ### Packstack 3 node @@ -109,7 +111,7 @@ encouraged to perform some of the following test scenarios. * CentOS 7 * Instructions: https://etherpad.openstack.org/p/amoralej-testday-newton-ga * Who: -* Results: +* Results: * Tickets: @@ -130,19 +132,19 @@ encouraged to perform some of the following test scenarios. * Tickets: -### TripleO Baremetal +### TripleO Baremetal * CentOS * Instructions: http://images.rdoproject.org/docs/baremetal/ -* Results: +* Results: * Tickets: -### TripleO Baremetal +### TripleO Baremetal * RHEL * Instructions: http://images.rdoproject.org/docs/baremetal/ * Who: -* Results: -* Tickets: +* Results: +* Tickets: ### TripleO Minimal virt deployment From 71b1fa8816a044132eca040a5e5616db0f2e4b69 Mon Sep 17 00:00:00 2001 From: Mary Thengvall Date: Tue, 16 Jan 2018 23:04:45 -0800 Subject: [PATCH 6/9] fixed various other links --- source/contribute/index.html.md | 2 +- source/documentation/selinux-issues.html.md | 6 +++--- source/documentation/trystack.html.md | 10 ++++++---- source/events/edit.html.md | 2 +- source/hardware/home/index.html.md | 2 +- source/hardware/minicluster.html.md | 3 +-- source/infra/review-rdo-infra-core.html.md | 2 +- source/install/packstack.html.md | 8 ++++---- ...ference-between-floating-ip-and-private-ip.html.md | 4 ++-- source/rdo/faq.html.md | 3 +-- source/rdo/rdo-videos.html.md | 2 +- source/resources/image-resources.html.md | 2 ++ ...workflow-to-manage-tripleo-life-cycle-full.html.md | 11 +++++------ .../Glance/using-swift-for-glance-with-rdo.html.md | 2 +- 14 files changed, 30 insertions(+), 29 deletions(-) diff --git a/source/contribute/index.html.md b/source/contribute/index.html.md index fa19b1bb9..84085e629 100644 --- a/source/contribute/index.html.md +++ b/source/contribute/index.html.md @@ -121,7 +121,7 @@ Join us for various [events](/events/) around the world. [Organize your own meet - Check our [Frequently Asked Questions (FAQ) page](/rdo/faq/) for answers to common questions - Try our [troubleshooting page](/troubleshooting/) for solutions to common problems - Watch [RDO videos](/rdo/rdo-videos). These include recorded talks and community events. -- Help improve our knowledge base by turning the best answers to questions on the [mailing lists](/contribute/mailing-lists/) or on [ask.openstack.org](http://ask.openstack.org) into a page in our [troubleshooting section](/troubleshooting/). In case of ask.openstack.org, a link might be sufficient. +- Help improve our knowledge base by turning the best answers to questions on the [mailing lists](/contribute/mailing-lists/) or on [ask.openstack.org](http://ask.openstack.org) into a page in our [troubleshooting section](/troubleshooting/). In case of [ask.openstack.org](https://ask.openstack.org), a link might be sufficient. - Blog about how you're using RDO. If you blog frequently about RDO and OpenStack, consider [requesting that your blog be added](https://wiki.openstack.org/wiki/AddingYourBlog) to the upstream [Planet OpenStack](http://planet.openstack.org/). - [Fork the website on Github](https://github.com/redhat-openstack/website) and help us improve our documentation. diff --git a/source/documentation/selinux-issues.html.md b/source/documentation/selinux-issues.html.md index 6b9df0569..e377760d7 100644 --- a/source/documentation/selinux-issues.html.md +++ b/source/documentation/selinux-issues.html.md @@ -45,12 +45,12 @@ For more information about how SELinux policies are developed for RDO, see [SELi ### PackStack fails if SELinux is disabled -It has been reported that [PackStack will fail if SELinux is disabled](http://{{SERVERNAME}}/forum/discussion/46/install-on-centos-6-4-and-selinux-disabled/p1). +It has been reported that PackStack will fail if SELinux is disabled. The error observed is: - ERROR : Error during puppet run : err: /Stage[main]//Exec[setenforce 0]/returns: - change from notrun to 0 failed: setenforce 0 returned 1 instead of one of [0] + ERROR : Error during puppet run : err: /Stage[main]//Exec[setenforce 0]/returns: + change from notrun to 0 failed: setenforce 0 returned 1 instead of one of [0] at /var/tmp/packstack/51a57c45478b4091b2eb6a1bbd4c2303/manifests/my_public_ip_ring_swift.pp:56 Please check log file /var/tmp/packstack/20130421-002212-fYYLUA/openstack-setup.log for more information diff --git a/source/documentation/trystack.html.md b/source/documentation/trystack.html.md index 4cbf98d32..303ff4c21 100644 --- a/source/documentation/trystack.html.md +++ b/source/documentation/trystack.html.md @@ -6,17 +6,19 @@ authors: dneary, sgordon # Using RDO on TryStack + -If you want to get familiar with the OpenStack dashboard interface, -and experiment with the creation of instances and shared volumes, -[TryStack](http://trystack.org) could be for you. +If you want to get familiar with the OpenStack dashboard interface, +and experiment with the creation of instances and shared volumes, +[TryStack](http://trystack.org) could be for you. TryStack is a public OpenStack cloud where you can try out OpenStack without having to set it up yourself. -If you connect to "OpenStack RDO Kilo on x86/RHEL", +If you connect to "OpenStack RDO Kilo on x86/RHEL", you will be connecting to a public sandboxed instance of RDO. diff --git a/source/events/edit.html.md b/source/events/edit.html.md index 2237d6ab0..013502545 100644 --- a/source/events/edit.html.md +++ b/source/events/edit.html.md @@ -5,7 +5,7 @@ title: Edit RDO events # Editing the RDO events calendar The RDO events calendar is maintained as part of the -[community.redhat.com](community.redhat.com) events site. To edit or add +[community.redhat.com](https://www.community.redhat.com) events site. To edit or add an RDO-related meetup, [edit this file](https://github.com/OSAS/rh-events/edit/master/2017/RDO-Meetups.yml) and send a pull request. If your event is some other community event, such as a mini-conference, [put it in this file instead](https://github.com/OSAS/rh-events/edit/master/2017/RDO-Community.yml). diff --git a/source/hardware/home/index.html.md b/source/hardware/home/index.html.md index 5ae0452e2..6a2e77816 100644 --- a/source/hardware/home/index.html.md +++ b/source/hardware/home/index.html.md @@ -20,7 +20,7 @@ it](mailto:rdo-list@redhat.com) and we'll add you to the list. |---|---| | [David Moreau Simard](https://twitter.com/dmsimard/status/778646409293733888)
[ ![](/images/homelab/dmsimard_home_lab.png) ](https://twitter.com/dmsimard/status/778646409293733888) | [Javier Peña](http://www.jpena.net/creating-a-home-openstack-lab-with-rdo-and-a-couple-spare-laptops/)
[ ![](/images/homelab/jpena.png) ](http://www.jpena.net/creating-a-home-openstack-lab-with-rdo-and-a-couple-spare-laptops/) | -| [Donny Davis](/hardware/home/donny_davis)
[ ![](/images/homelab/donny_davis_1_thumb.jpg) ](/hardware/home/donny_davis) | | +| [Donny Davis](http://project.fortnebula.com/)
[ ![](/images/homelab/donny_davis_1_thumb.jpg) ](/hardware/home/donny_davis) | | diff --git a/source/hardware/minicluster.html.md b/source/hardware/minicluster.html.md index fb55cf7f4..34e359630 100644 --- a/source/hardware/minicluster.html.md +++ b/source/hardware/minicluster.html.md @@ -21,8 +21,7 @@ On the RDO side, we built with the following hardware. | Cables | Various CAT5E cables for connectivity | | Switch | TP-LINK TL-SG105 | | Router | (Someone fill this in?) | -| USB network adapters | [Axago ADE-SG](http://www.axago.cz/cz/produkty/usb-adaptery/ADE-SG.html) or -similar | +| USB network adapters | [Axago ADE-SG](http://www.axagon.eu/produkty/ade-sg) or similar | Note: The NUCs have only one NIC. The USB network adapters are to diff --git a/source/infra/review-rdo-infra-core.html.md b/source/infra/review-rdo-infra-core.html.md index 1a9e31032..fda077e6e 100644 --- a/source/infra/review-rdo-infra-core.html.md +++ b/source/infra/review-rdo-infra-core.html.md @@ -52,7 +52,7 @@ The process to join the config-core group is: The following documentation can be useful when working on changes to the config repository: * [Introduction to Software Factory](https://www.rdoproject.org/blog/2017/06/introducing-Software-Factory-part-1/) -* [Software Factory user documentation](https://softwarefactory-project.io/docs/user/user.html) +* [Software Factory user documentation](https://softwarefactory-project.io/docs/user/index.html) * [Managing Software Factory resources via the config repository](https://softwarefactory-project.io/docs/user/resources_user.html#managing-resources-via-the-config-repository) * [Contents of the Software Factory config repository](https://softwarefactory-project.io/docs/operator/deepdive.html#the-config-repo) * [Jenkins Job Builder documentation](https://docs.openstack.org/infra/jenkins-job-builder/) diff --git a/source/install/packstack.html.md b/source/install/packstack.html.md index b38935c38..c84782c04 100644 --- a/source/install/packstack.html.md +++ b/source/install/packstack.html.md @@ -14,7 +14,7 @@ The instructions apply to the current **Pike** release. ## Summary for the impatient If you are using non-English locale make sure your `/etc/environment` is populated: - + LANG=en_US.utf-8 LC_ALL=en_US.utf-8 @@ -74,7 +74,7 @@ On RHEL, download and install the RDO repository RPM to set up the OpenStack rep ``` $ sudo yum install -y https://rdoproject.org/repos/rdo-release.rpm ``` - + On CentOS, the `Extras` repository provides the RPM that enables the OpenStack repository. `Extras` is enabled by default on CentOS 7, so you can simply install the RPM to set up the OpenStack repository. ``` @@ -108,7 +108,7 @@ Packstack takes the work out of manually setting up OpenStack. For a single node ``` $ sudo packstack --allinone ``` - + If you encounter failures, see the [Workarounds](/testday/workarounds/) page for tips. If you have run Packstack previously, there will be a file in your home directory named something like `packstack-answers-20130722-153728.txt` You will probably want to use that file again, using the `--answer-file` option, so that any passwords you have already set (for example, mysql) will be reused. @@ -119,4 +119,4 @@ Once the process is complete, you can log in to the OpenStack web interface Hori # Next steps -Now that your single node OpenStack instance is up and running, you can read on about [running an instance](/install/running-an-instance/), configuring a [floating IP range](/networking/floating-ip-range/), configuring RDO to [work with your existing network](/networking/neutron-with-existing-external-network/), or about expanding your installation by [adding a compute node](/install/adding-a-compute-node/). +Now that your single node OpenStack instance is up and running, you can read on about configuring a [floating IP range](/networking/floating-ip-range/), configuring RDO to [work with your existing network](/networking/neutron-with-existing-external-network/), or about expanding your installation by [adding a compute node](/install/adding-a-compute-node/). diff --git a/source/networking/difference-between-floating-ip-and-private-ip.html.md b/source/networking/difference-between-floating-ip-and-private-ip.html.md index 7b93ae2b3..05c504167 100644 --- a/source/networking/difference-between-floating-ip-and-private-ip.html.md +++ b/source/networking/difference-between-floating-ip-and-private-ip.html.md @@ -12,7 +12,7 @@ Are you wondering about the difference between a private IP address and a floati ## Private IP Address -A private IP address is assigned to an instance's network-interface by the DHCP server. The address is visible from within the instance by using a command like “ip a”. The address is typically part of a private network and is used for communication between instances in the same broadcast domain via virtual switch (L2 agent on each compute node). It can also be accessible from instances in other private networks via virtual router (L3 agent). +A private IP address is assigned to an instance's network-interface by the DHCP server. The address is visible from within the instance by using a command like “ip a”. The address is typically part of a private network and is used for communication between instances in the same broadcast domain via virtual switch (L2 agent on each compute node). It can also be accessible from instances in other private networks via virtual router (L3 agent). ## Floating IP Address @@ -24,7 +24,7 @@ A floating IP address and a private IP address can be used at the same time on a ## Example -A setup with 2 compute nodes, one Neutron controller (where the Neutron service, dhcp agent and l3 agent run), a physical router and a user. Let the physical subnet be 10.0.0.0/24. On the compute nodes instances are running using the private IP range 192.168.1.0/24. One of the instances is a webserver that should be reachable from a public network. Network outline: ![](neutron_private_floaring_ip.png "fig:neutron_private_floaring_ip.png") +A setup with 2 compute nodes, one Neutron controller (where the Neutron service, dhcp agent and l3 agent run), a physical router and a user. Let the physical subnet be 10.0.0.0/24. On the compute nodes instances are running using the private IP range 192.168.1.0/24. One of the instances is a webserver that should be reachable from a public network. Network outline: ![](neutron_private_floating_ip.png "fig:neutron_private_floating_ip.png") As shown in the picture above, the webserver is running on an instance with private IP 192.168.1.2. A User from network 10.0.0.0/24 wants to access the webserver but he's not part of private network 192.168.1.0/24. Using floating IP address 10.0.0.100 enables the user to fetch webpages from the webserver. The destination address is translated by the NAT table (iptables) within the virtual router deployed on the controller. diff --git a/source/rdo/faq.html.md b/source/rdo/faq.html.md index 3938c0830..e86b5ed06 100644 --- a/source/rdo/faq.html.md +++ b/source/rdo/faq.html.md @@ -42,7 +42,7 @@ RDO targets Red Hat Enterprise Linux, CentOS, and Fedora, and their derivatives. The OpenStack project develops code, and does not handle packaging for specific platforms. As a distribution of OpenStack, RDO packages the upstream OpenStack components to run well together on CentOS, Red Hat Enterprise Linux, Fedora, and their derivatives, and provides you with installation tools to make it easier for you to deploy OpenStack. -[Stable client branches](Clients) are maintained per release as part of RDO because client backward compatibility isn't guaranteed upstream. +[Stable client branches](release-cadence) are maintained per release as part of RDO because client backward compatibility isn't guaranteed upstream. ## How can I participate? @@ -103,4 +103,3 @@ RDO is built using CentOS infrastructure, similar to how CentOS packages are bui ## What is the relationship between RDO and Red Hat's commercial OpenStack product? RDO is a community-supported OpenStack distribution that tracks the latest version of OpenStack upstream, beginning with OpenStack Grizzly. [Red Hat OpenStack Platform](http://www.redhat.com/en/technologies/linux-platforms/openstack-platform) is an enterprise-ready commercially-supported product from Red Hat. - diff --git a/source/rdo/rdo-videos.html.md b/source/rdo/rdo-videos.html.md index fe4673b75..88c77c4d9 100644 --- a/source/rdo/rdo-videos.html.md +++ b/source/rdo/rdo-videos.html.md @@ -47,6 +47,6 @@ authors: dneary, rbowen, vaneldik ## Heat, OpenStack and Red Hat -* Interview with Steve Hardy at [Open World Forum 2013](//www.openworldforum.org/en/). +* Interview with Steve Hardy at Open World Forum 2013. diff --git a/source/resources/image-resources.html.md b/source/resources/image-resources.html.md index 6e5eb2528..844bc8730 100644 --- a/source/resources/image-resources.html.md +++ b/source/resources/image-resources.html.md @@ -22,7 +22,9 @@ You can run a number of different Linux distributions and operating systems on t ### Additional resources + * The [OpenStack Virtual Machine Image Guide](https://docs.openstack.org/image-guide/obtain-images.html) provides another list of Glance images ## Import images into Glance diff --git a/source/resources/use-a-ci-cd-workflow-to-manage-tripleo-life-cycle-full.html.md b/source/resources/use-a-ci-cd-workflow-to-manage-tripleo-life-cycle-full.html.md index 56045d931..c6b10a84b 100644 --- a/source/resources/use-a-ci-cd-workflow-to-manage-tripleo-life-cycle-full.html.md +++ b/source/resources/use-a-ci-cd-workflow-to-manage-tripleo-life-cycle-full.html.md @@ -128,7 +128,7 @@ We will also download a CentOS image used to build the Nodepool slaves, let's do curl -O http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2 openstack image create --disk-format qcow2 --container-format bare --file ~/CentOS-7-x86_64-GenericCloud.qcow2 centos7-cloud -We can now deploy Software Factory using heat templates ([documentation](https://softwarefactory-project.io/docs/deploy.html)) +We can now deploy Software Factory using heat templates ([documentation](https://softwarefactory-project.io/docs/operator/deployment.html?highlight=deploy#deploying-with-heat)) image_id=$(openstack image show sf-2.3.0 -f value -c id) key_name="sf-key" @@ -347,7 +347,7 @@ You need to get the **credential-id** for each resource, select your credential, ![](/images/sf-credential_id.png) -We have a Software Factory instance and a nodepool project with 2 slaves, it's now time to create demo-sf-tripleo project. We will use the new management system via the config repository ([documentation](https://softwarefactory-project.io/docs/resources_user.html#resources-user)). In the config directory, create resources/demo-tripleo.yaml with the following content: +We have a Software Factory instance and a nodepool project with 2 slaves, it's now time to create demo-sf-tripleo project. We will use the new management system via the config repository ([documentation](https://softwarefactory-project.io/docs/user/index.html)). In the config directory, create resources/demo-tripleo.yaml with the following content: # resources/demo-tripleo.yaml resources: @@ -439,10 +439,10 @@ It's time to create our job, in config repository directory, create a file jobs/ In this file we create a project named demo-sf-tripleo. We define 2 jobs for our project, the first one is a default job (it will run run_tests.sh that we will create in our project repository), the second one is a custom job we define later on the file). With the last statement, we specify the node (label) used to run the jobs. -In the second part, we define the custom **deploy** job ([job documentation](https://softwarefactory-project.io/docs/jenkins_user.html)). +In the second part, we define the custom **deploy** job ([job documentation](https://softwarefactory-project.io/docs/project_config/jenkins_user.html)). -Now, we will create a file, zuul/tripleo.yaml with this content to define which job will be executed by each pipeline ([pipelines documentation](https://softwarefactory-project.io/docs/zuul_user.html#pipelines-default-configuration). +Now, we will create a file, zuul/tripleo.yaml with this content to define which job will be executed by each pipeline ([pipelines documentation](https://softwarefactory-project.io/docs/project_config/zuul_user.html#pipelines-default-configuration)). projects: - name: demo-sf-tripleo @@ -662,7 +662,7 @@ cat << EOF > patches/add_update_cmd_ovb_shell.patch @@ -294,5 +294,25 @@ undercloud.ssh_pool.stop_all() exit(0) - + + if step == 'update': + provisioner = config['provisioner'] + templates = provisioner.get('heat_templates_dir') @@ -756,4 +756,3 @@ You can source overcloudrc openrc file if you want to interact with the deployed ### Update Openstack To update the openstack, you can edit the template file or add another template (update the deployment command), summit a review, validate it. The update command will be applied on the deployed openstack. If you want to do another deployment, you have to delete all the servers within sf-tripleo project, and push a reivew. - diff --git a/source/storage/Glance/using-swift-for-glance-with-rdo.html.md b/source/storage/Glance/using-swift-for-glance-with-rdo.html.md index 86bf9fcea..fbed3e9c7 100644 --- a/source/storage/Glance/using-swift-for-glance-with-rdo.html.md +++ b/source/storage/Glance/using-swift-for-glance-with-rdo.html.md @@ -7,7 +7,7 @@ authors: coolsvap The default backend driver configured for Glance is the local filesystem but it supports a set of alternative backends, including Swift. If you want to store the Glance images on Swift, a few post-install configuration steps are needed: ` # openstack-config --set /etc/glance/glance-api.conf DEFAULT default_store swift` - ` # openstack-config --set /etc/glance/glance-api.conf DEFAULT swift_store_auth_address `[`http://$KEYSTONE_HOST:5000/v2.0/`](http://$KEYSTONE_HOST:5000/v2.0/) + ` # openstack-config --set /etc/glance/glance-api.conf DEFAULT swift_store_auth_address http://$KEYSTONE_HOST:5000/v2.0/` ` # openstack-config --set /etc/glance/glance-api.conf DEFAULT swift_store_user services:glance` ` # openstack-config --set /etc/glance/glance-api.conf DEFAULT swift_store_key $SERVICE_PASSWORD` ` # openstack-config --set /etc/glance/glance-api.conf DEFAULT swift_store_create_container_on_put True` From 2ab0125f26f451b94f62d0a4ef508d7389f04aa6 Mon Sep 17 00:00:00 2001 From: Mary Thengvall Date: Thu, 18 Jan 2018 10:12:16 -0800 Subject: [PATCH 7/9] last batch of bad links --- .../2016/ceph-rdo-barcelona/jpena.html | 1989 ----------------- source/events/rdo-day-fosdem-2016.html.md | 6 +- source/infra/index.html.md | 7 +- source/infra/service-continuity.html.md | 2 +- source/rdo/index.html.md | 3 +- source/testday/index.html.md | 4 +- 6 files changed, 9 insertions(+), 2002 deletions(-) delete mode 100644 source/events/presentations/2016/ceph-rdo-barcelona/jpena.html diff --git a/source/events/presentations/2016/ceph-rdo-barcelona/jpena.html b/source/events/presentations/2016/ceph-rdo-barcelona/jpena.html deleted file mode 100644 index 6a7585a84..000000000 --- a/source/events/presentations/2016/ceph-rdo-barcelona/jpena.html +++ /dev/null @@ -1,1989 +0,0 @@ - - - - - - - RDO repos overview: Slides - - - - - - - - - - - - -
-
-
-

           repos overview

- -

 

- -

 

- -

Javier Peña

- -

25-Oct-2016

-
-
-

THINK RDO REPOS ARE CONFUSING?

- -

Don't know which to use?

-
-
-

OK, it'S not that confusing

-
-
-
    -
  • Stable
    • -
  • Testing
    • -
  • Trunk
    • -
-
-

Stable

-
-
-
    -
  • - 
    http://mirror.centos.org/centos/7/cloud/x86_64/openstack-<branch>/
    -
    • -
  • Signed packages: Yes!
    • -
  • Source: released project tags (*)
    • -
  • Creation: manual tagging of packages in testing repo
    • -
  • Use for: production
    • -
-
-
-

(*) Unless your project is too lazy to release tags :P

-
-

TESTING

-
-
-
    -
  • - 
    http://buildlogs.centos.org/centos/7/cloud/x86_64/openstack-<branch>/
    -
    • -
  • Signed packages: No
    • -
  • Source: released project tags (*)
    • -
  • Creation: automated after spec change review, manual tagging
    • -
  • -Use for: -
      -
    • Updates (if can't wait for stable)
      • -
    • Testing packages before going to stable
      • -
    -
    • -
-
-
-

(*) Unless your project is too lazy to release tags :P

-
-

TRUNK

-
-
    -
  • -
    http://trunk.rdoproject.org/centos7-<branch>/
    -
    • Where branch is [master-head|master|newton|mitaka|liberty]
    -
    • -
  • Signed packages: No
    • -
  • -Source: current upstream GitHub repo HEAD (*)
    -
    • -
  • Creation: automated
    • -
  • -Use for:
      -
    • Updates (if can't wait for testing/stable)
      • -
    • CI jobs
      • -
    -
    • -
-
-

(*) Exception for certain projects in centos7-master, that are pinned to their released versions in

- -

upper-constraints.txt

-
-

You can help, too!

-
-
-
-

Different branches:

- -
    -
  • rpm-master: for trunk
    • -
  • newton-rdo: for stable/testing/trunk
    • -
- -

Reviews at review.rdoproject.org

-
-

LESS CONFUSED NOW?

-
-
-

ASK questions!

-
-
-
- -
- - - - - - - - - - - - - diff --git a/source/events/rdo-day-fosdem-2016.html.md b/source/events/rdo-day-fosdem-2016.html.md index 212fe9eb5..ef97c84b9 100644 --- a/source/events/rdo-day-fosdem-2016.html.md +++ b/source/events/rdo-day-fosdem-2016.html.md @@ -6,7 +6,7 @@ authors: rbowen # RDO Community Day @ FOSDEM 2016 RDO Community Day at FOSDEM 2016 was held in conjunction with the [CentOS -Dojo](https://wiki.centos.org/Events/Dojo/Brussels2016) on the day +Dojo](https://wiki.centos.org/Events/Dojo/Brussels2016) on the day before FOSDEM. The schedule of talks was as follows: @@ -66,7 +66,7 @@ allowfullscreen> ## RDO configuration files: do's, dont's, gotchas, and rfc - *Ihar Hrachyshka* -[[Slides](./presentations/2016/FOSDEM/./configuration-files-in-rdo-fosdem-2016.pdf)] +[[Slides](./presentations/2016/FOSDEM/configuration-files-in-rdo-fosdem-2016.pdf)] > This presentation will give overview of how we configure OpenStack services, in general as well from RDO perspective. Audience should expect brief overview of libraries and techniques used in upstream to manage configuration, new developments in upstream, things to consider when doing packaging for RDO and derived distributions, things upstream projects do wrong about configurations, and how to fix it. At the end, I will present configuration scheme Neutron RDO packages adopted in Kilo+, and suggest it for wider adoption by other projects. @@ -90,5 +90,3 @@ allowfullscreen> [[Slides](http://www.slideshare.net/flepied/rpm-factory-for-rdo)] > How to use an OpenStack like workflow to build RDO packages - - diff --git a/source/infra/index.html.md b/source/infra/index.html.md index ac1f9ce56..8881ef600 100644 --- a/source/infra/index.html.md +++ b/source/infra/index.html.md @@ -29,7 +29,7 @@ In addition to this, a separate DLRN instance is supporting the upstream [rpm-packaging](https://github.com/openstack/rpm-packaging) project with up to date packages built from its spec templates, [rpm-packaging-ci.rdoproject.org](https://rpm-packaging-ci.rdoproject.org/repos/status_report.html). -## Code Review and CI +## Code Review and CI The RDO Gerrit instance is running at [review.rdoproject.org](https://review.rdoproject.org/). It makes use of a pool of VMs for CI managed by nodepool and running on the RDO Cloud. @@ -55,7 +55,7 @@ High-level status dashboards for the RDO project. ## Status -[status.rdoproject.org](http://status.rdoproject.org/) +[status.rdoproject.org](http://status.rdoproject.org/) aggregates status and monitoring information from the different systems part of the RDO infrastructure. @@ -70,7 +70,7 @@ The code lives on several organizations at GitHub: * [Package specs](https://github.com/rdo-packages) * [Infrastructure definition and CI](https://github.com/rdo-infra) -* [Website, rdoinfo and others](https://github.com/redhat-openstack) +* [Website, rdoinfo and others](https://github.com/redhat-openstack) ## Processes and maintenance windows @@ -87,4 +87,3 @@ A number of parts of our infrastructure run at CentOS, including * [CI](https://ci.centos.org/view/rdo/view/promotion-pipeline/) * [CentOS Cloud SIG](https://wiki.centos.org/SpecialInterestGroup/Cloud) (not infrastructure, but governance/process) - diff --git a/source/infra/service-continuity.html.md b/source/infra/service-continuity.html.md index 25bfaecce..d53102009 100644 --- a/source/infra/service-continuity.html.md +++ b/source/infra/service-continuity.html.md @@ -52,7 +52,7 @@ The following table details the high-level plan for each service. A link to a de | DLRN DB instance | High |DB will be synced to a slave instance in the offsite cloud. In case of an outage to the RDO cloud, we can set the slave instance as master, and re-configure DLRN instances to use it. | | | DLRN instance for upstream rpm-packaging | Medium | Built repos can be synced using rsync to https://trunk.rdoproject.org (in the offsite cloud). In case of an outage in the RDO cloud, we can switch the DNS entry to the machine in trunk.rdoproject.org (maybe some vhost is needed here????). | | | images.rdoproject.org (+ CI docker registry) | High | Rsync to machine in offsite cloud. In case of an outage in the RDO cloud, we can switch the DNS entry to the machine in the offsite cloud. || -| www.rdoproject.org | High | Web contents are static and stored in . In case of an outage, we can switch the DNS entry to a machine in the offsite cloud. The builder and web deployment are maintained by OSAS at rdo-web-builder.osci.io and can be recreated using Ansible ()) | For rdo-release.rpm rdoproject.org redirects to . This is out of RDO infra but is used by different CI jobs and users. *I assume repos.fedorapeople.org has its own replication/DR, right?*| +| www.rdoproject.org | High | Web contents are static and stored in . In case of an outage, we can switch the DNS entry to a machine in the offsite cloud. The builder and web deployment are maintained by OSAS at rdo-web-builder.osci.io and can be recreated using Ansible ()) | For rdo-release.rpm rdoproject.org redirects to . This is out of RDO infra but is used by different CI jobs and users. *I assume repos.fedorapeople.org has its own replication/DR, right?*| | blogs.rdoproject.org | Medium | Previous Enovance blog, still has content published from time to time. Machine is unmaintained (old Debian Squeeze and old WordPress). Needs rework.|| | planet.rdoproject.org | Low | Hosted on Rich's VPS | | | dashboards.rdoproject.org | Low | Hosted on the same VM as www. | Deployed using ansible like www. | diff --git a/source/rdo/index.html.md b/source/rdo/index.html.md index c3df84ff4..ad99060a3 100644 --- a/source/rdo/index.html.md +++ b/source/rdo/index.html.md @@ -18,7 +18,7 @@ indicate that they need, and what the community steps up to package. * [FAQ](/rdo/faq) * [Bugzilla ownership](/rdo/bugzilla-ownership) * [CentOS](/rdo/centos) -* [Continuous Integration](/rdo/continuous-integration) +* [Continuous Integration](/infra#codereview-ci) * [Videos](/rdo/rdo-videos) * [Release Cadence](/rdo/release-cadence) @@ -27,4 +27,3 @@ indicate that they need, and what the community steps up to package. If you are happy with community support, and what you want is to use and test the latest version of OpenStack, then RDO is for you. If, however, what you are looking for is a stable, supported platform, with certification of partner applications, and a reliable partner with a great track record in enterprise infrastructure to build or scale out your production OpenStack cloud, consider [Red Hat OpenStack Platform](https://www.redhat.com/en/technologies/linux-platforms/openstack-platform). - diff --git a/source/testday/index.html.md b/source/testday/index.html.md index f30ddbe34..41ad2c940 100644 --- a/source/testday/index.html.md +++ b/source/testday/index.html.md @@ -21,7 +21,7 @@ We would love to hear about your experiences, with either a [Packstack installation](/install/packstack) or the [TripleO Quickstart](/tripleo). We also encourage you to work through the [upstream installation -tutorial](https://docs.openstack.org/draft/install-guide-rdo/) +tutorial](https://docs.openstack.org/queens/install/) while keeping detailed notes on the following points: * Did you know what the document assumed that you'd know? @@ -46,7 +46,7 @@ while keeping detailed notes on the following points: | Newton 2 | July 28-29 | 2 | | [Tickets](https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&chfield=%5BBug%20creation%5D&chfieldfrom=2016-07-27&chfieldto=2016-07-30&classification=Community&list_id=4344410&product=RDO&query_format=advanced) | | Newton 1 | June 8-9 | 15 | 33 participants, 408 messages | [Tickets](https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&chfield=%5BBug%20creation%5D&chfieldfrom=2016-06-08&chfieldto=2016-06-11&classification=Community&list_id=4344410&product=RDO&query_format=advanced) | | Mitaka GA | April 13-14 | 6 | | [Tickets](http://tm3.org/rdo-mitaka-test) | -| Mitaka 3 | March 10-11, 2016 | 14 | | [Tickets](https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&chfield=%5BBug%20creation%5D&chfieldfrom=2016-03-09&chfieldto=2016-03-12&classification=Community&list_id=4344410&product=RDO&query_format=advanced) | +| Mitaka 3 | March 10-11, 2016 | 14 | | [Tickets](https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&chfield=%5BBug%20creation%5D&chfieldfrom=2016-03-09&chfieldto=2016-03-12&classification=Community&list_id=4344410&product=RDO&query_format=advanced) | | Mitaka 1 | Dec 10-11, 2015 | 9 | 44 participants, 795 messages | [Tickets](https://goo.gl/51Dz97) | | Liberty 2 | Oct 12-13 | 23 | 42 participants, 1074 messages | [Tickets](https://goo.gl/D6VeQ0) | | Liberty 1 | Sep 23-24 | 17 | | [Tickets](https://goo.gl/OIPNt3) | From 45575e753aca8298909f709df381ae3c4a11e7c8 Mon Sep 17 00:00:00 2001 From: Mary Thengvall Date: Thu, 18 Jan 2018 10:21:52 -0800 Subject: [PATCH 8/9] resolve conflicts --- source/infra/index.html.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/source/infra/index.html.md b/source/infra/index.html.md index 8881ef600..52c898424 100644 --- a/source/infra/index.html.md +++ b/source/infra/index.html.md @@ -53,11 +53,14 @@ Wordpress blog site for RDO engineers. High-level status dashboards for the RDO project. [dashboards.rdoproject.org](https://dashboards.rdoproject.org/rdo-dev) +<<<<<<< bad-links-011618 ## Status [status.rdoproject.org](http://status.rdoproject.org/) aggregates status and monitoring information from the different systems part of the RDO infrastructure. +======= +>>>>>>> master ## Planet From ac503913805b230c74bf7b9aeee4964f1d3a8ab6 Mon Sep 17 00:00:00 2001 From: Mary Thengvall Date: Fri, 26 Jan 2018 21:19:34 -0800 Subject: [PATCH 9/9] took out www in community.redhat.com --- source/events/edit.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/events/edit.html.md b/source/events/edit.html.md index 013502545..059ba2cbd 100644 --- a/source/events/edit.html.md +++ b/source/events/edit.html.md @@ -5,7 +5,7 @@ title: Edit RDO events # Editing the RDO events calendar The RDO events calendar is maintained as part of the -[community.redhat.com](https://www.community.redhat.com) events site. To edit or add +[community.redhat.com](https://community.redhat.com) events site. To edit or add an RDO-related meetup, [edit this file](https://github.com/OSAS/rh-events/edit/master/2017/RDO-Meetups.yml) and send a pull request. If your event is some other community event, such as a mini-conference, [put it in this file instead](https://github.com/OSAS/rh-events/edit/master/2017/RDO-Community.yml).