cloud April 2017

cloud@lists.stg.fedoraproject.org

20 participants
123 discussions

[atomic-wg] Issue #266: rpmostree_compose Ansible module
by Trishna Guha 28 Jun '17

28 Jun '17

trishnag reported a new issue against the project: `atomic-wg` that you are following: `` As for Ansible module for atomic host we have `atomic_host` and `atomic_image` modules written. The plan/purpose of this ticket is to have rpm-ostree modules get done for Ansible as well. We can perhaps have all the `rpm-ostree` options as Ansible modules so that we really do not need to execute rpm-ostree commands as part of `shell`/`command` modules in Ansible. I wrote `rpmostree compose` Ansible module: https://github.com/ansible/ansible/pull/23209. Can anyone volunteer to review the PR? Bringing in @dustymabe @jberkus @walters @jlebon here. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/266

2 1

[atomic-wg] Issue #263: open up read permission on our AMIs
by Dusty Mabe 26 Jun '17

26 Jun '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` A [BZ](https://bugzilla.redhat.com/show_bug.cgi?id=1423753) came in that requested we open up read permission on our AMIs Sayan wrote a script to do this: https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org… Where are we on getting this done? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/263

3 16

[atomic-wg] Issue #230 `enable ostree gpg verification in our baked images`
by Dusty Mabe 26 Jun '17

26 Jun '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` Now that ostree metadata is signed we should start configuring our media so that the resulting systems verify signatures with something like this: ``` # cat /etc/ostree/remotes.d/fedora-atomic.conf [remote "fedora-atomic"] url=https://dl.fedoraproject.org/pub/fedora/linux/atomic/25/ gpg-verify=true gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-primary ``` Are there any issues that need to be resolved first? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/230

2 10

Announce: Fedora Layered Image Release
by Adam Miller 13 Jun '17

13 Jun '17

4 18

[atomic-wg] Issue #252 `Fix rawhide ISO`
by Colin Walters 01 Jun '17

01 Jun '17

walters reported a new issue against the project: `atomic-wg` that you are following: `` https://kojipkgs.fedoraproject.org/compose/rawhide/latest-Fedora-Rawhide/lo… ``` Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/pylorax/ltmpl.py", line 56, in parse textbuf = template.render(**variables) File "/usr/lib/python3.6/site-packages/mako/template.py", line 462, in render return runtime._render(self, self.callable_, args, data) File "/usr/lib/python3.6/site-packages/mako/runtime.py", line 838, in _render **_kwargs_for_callable(callable_, data)) File "/usr/lib/python3.6/site-packages/mako/runtime.py", line 873, in _render_context _exec_template(inherit, lclcontext, args=args, kwargs=kwargs) File "/usr/lib/python3.6/site-packages/mako/runtime.py", line 899, in _exec_template callable_(context, *args, **kwargs) TypeError: render_body() missing 1 required positional argument: 'root' ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/252

2 6

[atomic-wg] Issue #181 `Vagrant cannot create synced folder`
by Pagure 26 May '17

26 May '17

jorti reported a new issue against the project: `atomic-wg` that you are following: `` I just launch an unmodified fedora/25-atomic-host box and I get the error that it cannot create the /vagrant synced dir. ``` $ vagrant up Bringing machine 'default' up with 'libvirt' provider... ==> default: Creating image (snapshot of base box volume). ==> default: Creating domain with the following settings... ==> default: -- Name: mail-server_default ==> default: -- Domain type: kvm ==> default: -- Cpus: 1 ==> default: -- Memory: 512M ==> default: -- Management MAC: ==> default: -- Loader: ==> default: -- Base box: fedora/25-atomic-host ==> default: -- Storage pool: default ==> default: -- Image: /var/lib/libvirt/images/mail-server_default.img (41G) ==> default: -- Volume Cache: default ==> default: -- Kernel: ==> default: -- Initrd: ==> default: -- Graphics Type: vnc ==> default: -- Graphics Port: 5900 ==> default: -- Graphics IP: 127.0.0.1 ==> default: -- Graphics Password: Not defined ==> default: -- Video Type: cirrus ==> default: -- Video VRAM: 9216 ==> default: -- Keymap: en-us ==> default: -- TPM Path: ==> default: -- INPUT: type=mouse, bus=ps2 ==> default: -- Command line : ==> default: Creating shared folders metadata... ==> default: Starting domain. ==> default: Waiting for domain to get an IP address... ==> default: Waiting for SSH to become available... default: default: Vagrant insecure key detected. Vagrant will automatically replace default: this with a newly generated keypair for better security. default: default: Inserting generated public key within guest... default: Removing insecure key from the guest if it's present... default: Key inserted! Disconnecting and reconnecting using new SSH key... ==> default: Configuring and enabling network interfaces... ==> default: Rsyncing folder: /home/juan/Vagrant/mail-server/ => /vagrant The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! mkdir -p /vagrant Stdout from the command: Stderr from the command: mkdir: cannot create directory ‘/vagrant’: Operation not permitted ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/181

2 6

doctl package for Fedora
by Dusty Mabe 18 May '17

18 May '17

Anyone interested in packaging up Digital Ocean's CLI for Fedora? https://github.com/digitalocean/doctl Dusty

4 7

Proposal: Release blocking for F27
by Colin Walters 11 May '17

11 May '17

https://bugzilla.redhat.com/show_bug.cgi?id=1435310 raised the issue that apparently, Atomic Host isn't "release blocking". I think we have plenty of resources to match whatever criteria there are for that for Fedora 27. Thoughts?

10 20

[atomic-wg] Issue #270: Update getfedora.org with Digital Ocean
by Josh Berkus 09 May '17

09 May '17

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Since we're about to have general availability on DO, we want to change GetFedora.org to reflect that. 1. Change the "Amazon" section on https://getfedora.org/en/atomic/download/ to be "Public Cloud" (see suggested title and text below). 2. Combine the two selector boxes for GP2 and Standard instances into one selector box with an extra column called "Storage" which is either "GP2" or "Standard". Label the button which triggers this box "AWS Cloud" 3. Add a new button called "Digital Ocean", which will trigger a similar selector box to the AWS selector, for DO instances. Suggested Text: Public Cloud Images for Amazon EC2 and Digital Ocean The links below will provide you listings of available Atomic Host instances on two public clouds, Amazon EC2 and Digital Ocean. If you already have an account on these clouds, this will provide you one-click launch of an Atomic Host instance. @dustymabe @jligon @robyduck `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/270

4 4

Re: [atomic-devel] Storage for system containers
by Daniel Walsh 30 Apr '17

30 Apr '17

On 04/28/2017 01:09 PM, Giuseppe Scrivano wrote: > Hi, > > Dusty Mabe <dusty(a)dustymabe.com> writes: > >> i'm going to show how little I know with this question, but would it be possible >> to have a separate partition for system containers that was essentially xfs + an >> overlayfs of the host filesystem? > yes we could do that, we will just need to use a separate OSTree > repository, so that it won't be shared with the OS. This is possible > already today, as the OSTree storage to use is configurable. > The disadvantage is that files in common with the host will still need > to be copied in the new repository. > > Regards, > Giuseppe Ok, We should be able to support both environments, where you want to maximize disk space savings by taking advantage of sharing OS Content with the Host OS by running your system container storage on the same disk as /usr. If you want to totally isolate your container content from the host, we can mount /var/lib/containers on an separate partition/disk and keep storage isolated. The only problem here is that /var/lib/docker would need to be modified to use /var/lib/containers/docker. From CRI-O/buildah and all container storage we store by default in /var/lib/containers/storage. With the move to ThePackageFormallyKnownAsDocker (TPFKAD), we should move the default storage to /var/lib/containers/TPFKAD.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud April 2017