Closed
Bug 942253
Opened 12 years ago
Closed 12 years ago
[tracker] build new stackato 2.10.6 dev paas
Categories
(Infrastructure & Operations :: IT-Managed Tools, task)
Infrastructure & Operations
IT-Managed Tools
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: cturra, Assigned: cturra)
References
Details
(Whiteboard: [qa-])
tracker bug for the work being done to upgrade the dev paas from v. 2.6.7 to 2.10.6.
Assignee | ||
Comment 1•12 years ago
|
||
time for an update \o/
i have completed building the infrastructure for this new dev stackato cluster. my goal is to initially launch with a similar setup to the existing cluster (running 2.10.6). once that launch is complete, we will add additional dea/stager nodes as required by resource demand.
my next steps are to test out importing the existing clusters application/service data into the new dev cluster. to do this, i need to take a short downtime on the core and services nodes (needed to take a data snapshot). i am going to propose doing this work tonight after hours (pacific time) - an email will be going out to the paas mail-list on this topic.
after this data export is complete, i will be able to work through the procedures of migrating to a new version (this is uncharted waters for us, but i have been speaking with activestate on the topic).
Assignee | ||
Comment 2•12 years ago
|
||
yesterday evening i completed an export of the current dev environment and am actively working on testing the import into our new (2.10.6) environment. stay tuned for more info on the results of that work.
Assignee | ||
Comment 3•12 years ago
|
||
update time! i made good progress on the import (migration) testing from the 2.6.7 dev cluster. currently, all user/groups are present and services are functioning as expected. there are still some outstanding items to sort out with regards to applications. many are starting correctly in the new 2.10.6 cluster (wee!), but i have noticed there is some discrepancy in the frameworks that should be available. i will continue working on that today and see where i get.
Assignee | ||
Comment 4•12 years ago
|
||
during the dev migration testing, it became obvious we were going to need much more horse power for the stager and dea nodes. over the weekend i deployed a third stager/dea node in this new dev cluster *and* added two more CPUs to each dea/stager vm. this looks to have gotten us to a point where we can manage the existing load.
in addition to this work, i have sent out an email to the paas mail list to have everyone audit their current applications in the existing dev environment. there appears to be many necessary test applications that can probable be removed. this would free up some resources and make the final migration work much cleaner.
https://mail.mozilla.org/pipermail/paas-users/2013-December/000140.html
Assignee | ||
Comment 5•12 years ago
|
||
as mentioned in my last email to the paas mail list, i'd like to move forward with the migration to the new 2.10.6 dev paas starting today at noon (pacific time). more details can be found in this message if you missed my email:
https://mail.mozilla.org/pipermail/paas-users/2013-December/000145.html
Assignee | ||
Comment 6•12 years ago
|
||
migration work complete! we now have a functional 2.10.6 dev cluster \o/
more notes can be found in my email to the paas mail list:
https://mail.mozilla.org/pipermail/paas-users/2013-December/000147.html
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•