#1659 doc: simplify instructions for AWS image creation
Merged 3 years ago by praiskup. Opened 3 years ago by praiskup.
Unknown source update-docs-new-builders  into  master

file modified
+10 -18
@@ -154,11 +154,7 @@

  Prepare AWS source images

  -------------------------

  

- First, check that `AWS login link`_ works fine for you, and that you are

- successfully logged-in.  Otherwise the following steps won't redirect you

- properly to AWS web console.

- 

- Then you need to find proper (official) ``ami-*`` Fedora image IDs, bound to

+ You need to find proper (official) ``ami-*`` Fedora image IDs, bound to

  your desired VM location.  You can e.g. go to `Fedora Cloud Page`_ and search

  for ``GP2 HVM AMIs`` (for x86_64) and ``arm64 AMIs`` (for aarch64) sections.

  
@@ -166,13 +162,11 @@

  new window should appear (javascript) with a list of available server locations.

  So you see the small "blue cloud" icon/hyperlink related to the desired server

  location (we are using N.Virginia option, aka ``us-east-1``, but we should move

- to ``us-west-*`` soon).  Check what address the button points to::

- 

-     https://redirect.fedoraproject.org/console.aws.amazon.com/ec2/v2/home

-         ?region=us-east-1#LaunchInstanceWizard:ami=ami-0c830793775595d4b

+ to ``us-west-*`` soon).

  

- Do not click the launch button and do not proceed to launch the instance manually

- through Amazon AWS launcher. Only remember the ``ami-0c830793775595d4b`` ID part.

+ Do not click the launch button and do not proceed to launch the instance

+ manually through Amazon AWS launcher. Only remember the

+ ``ami-0c830793775595d4b`` ID part.

  

  Then ssh to ``root@copr-be-dev.cloud.fedoraproject.org``, and ``su - copr``, and

  execute::
@@ -314,9 +308,7 @@

  You can try to kill all the old currently unused builders, and check the spawner

  log what is happening::

  

-     [copr@copr-be-dev ~][STG]$ cleanup_vm_nova.py --kill-also-unused

-     [copr@copr-be-dev ~][STG]$ cleanup-vms-aws --kill-also-unused

-     [copr@copr-be-dev ~][STG]$ tail -f /var/log/copr-backend/spawner.log

+     [copr@copr-be-dev ~][STG]$ resalloc-maint resource-delete $(resalloc-maint resource-list | grep ticket=NULL | grep status=UP | cut -d' ' -f1)

Oh, I like this one :-)

  

  

  Production
@@ -332,11 +324,11 @@

          -l copr-be.aws.fedoraproject.org groups/copr-backend.yml \

          -t provision_config

  

- Optionally, when you need to propagate the builders quickly, you can terminate

- the old currently unused builders by::

+ Optionally, when you need to propagate the new images quickly, you can terminate

+ the old but currently unused builders by::

  

-     $ cleanup_vm_nova.py --kill-also-unused

-     $ cleanup-vms-aws --kill-also-unused

+     $ su - resalloc

+     $ resalloc-maint resource-delete $(resalloc-maint resource-list | grep ticket=NULL | grep status=UP | cut -d' ' -f1)

  

  .. _`staging backend box`: https://copr-be-dev.cloud.fedoraproject.org

  .. _`Fedora Infra OpenStack`: https://fedorainfracloud.org

At that point in time, user doesn't need to have access to AWS web UI
actually. It is enough to have access to the copr-be-dev machine.

1 new commit added

  • doc: correctly document how to terminate old builders
3 years ago

rebased onto cfa81c92d64e4ab439f12612210aaa7552562896

3 years ago

rebased onto 72ba5b4

3 years ago

Pull-Request has been merged by praiskup

3 years ago
Metadata