September 2016 - cloud - Fedora Mailing-Lists

[cloud] #120: Fedora 22 Cloud vagrant image does not extend filesystem to disk size

by Fedora Cloud Trac Tickets

#120: Fedora 22 Cloud vagrant image does not extend filesystem to disk size ------------------------------+-------------------- Reporter: pwnall | Owner: Type: defect | Status: new Priority: normal | Milestone: Future Component: Cloud Base Image | Keywords: ------------------------------+-------------------- Copied from RHBZ #1260800, based on responses seen on other bugs related to the Vagrant image. Description of problem: The Vagrant image for Fedora 22 cloud does not extend the filesystem to fill up the entire disk. Version-Release number of selected component (if applicable): https://download.fedoraproject.org/pub/fedora/linux/releases/22/Cloud/x86... /Fedora-Cloud-Base-Vagrant-22-20150521.x86_64.vagrant-virtualbox.box How reproducible: Always Steps to Reproduce: 1. Set up a new Vagrant box using the Fedora 22 cloud base box. 2. vagrant ssh 3. Inspect the partition table. Actual results: [vagrant@localhost ~]$ sudo fdisk -l /dev/sda Disk /dev/sda: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xe02b2711 Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 6146047 6144000 3G 83 Linux Expected results: I'd expect to see the filesystem grown to fill the virtual disk. Additional info: This is a serious obstacle to deploying Fedora Cloud for me. I need to be able to test things out in a Vagrant box before pushing things out to production. The 3G filesystem makes it impossible for me to load everything I need into the VM. Please let me know if there is any other information I can provide to help narrow this down. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/120> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

7 years, 6 months

1
10
0 / 0

[cloud] #34: External need: batched updates

by Fedora Cloud Trac Tickets

#34: External need: batched updates --------------------+------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Flock 2014 Component: --- | Keywords: --------------------+------------------------ '''Summary:''' We want to produce updated images on a monthly cadence. It would be nice if we could produce those from QA'd bunches of packages. '''Importance:''' moderate (it will be hard to implement image refresh without this, but we could do it) '''Timeframe:''' F21 release + 1 month / Obviously better if we get things lined up earlier '''Fedora Sub-Project/SIG:''' Primarily QA, but Rel Eng and Infrastructure too. This is pretty big. ''' Cloud SIG owner:''' TBD (this probably needs someone actively contributing to initial and ongoing work) See the related Change proposal "(A)Periodic Updates to the Images" http://flock2013.sched.org/event/8c4f702e42814598e0e4e31b188a0ae6 What's this ticket about? We need an owner for this — someone to drive it forward. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/34> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

7 years, 6 months

1
2
0 / 0

[cloud] #110: Make NFS file sync work with Vagrant seamlessly

by Fedora Cloud Trac Tickets

#110: Make NFS file sync work with Vagrant seamlessly ------------------------------+-------------------------- Reporter: rtnpro | Owner: rtnpro Type: task | Status: new Priority: normal | Milestone: Fedora 22 Component: Software Updates | Keywords: vagrant, nfs ------------------------------+-------------------------- Issues ====== 1. Vagrant 1.7.2 does not identify proper flavor for Fedora, so, during starting NFS client services in a Fedora guest, it fails. This issue seems to have been fixed in Vagrant's master branch. We need to patch the current RPM package for vagrant with the fixes. 2. By default vagrant guest OS tries to communicate to NFS server in the host Fedora box using NFS v3 and it fails. It works correctly if we explicitly ask vagrant to use NFS v4 using nfs_version: 4. This needs to be documented for Fedora properly. 3. The biggest obstacle is mapping UID, GID from host OS to guest OS for NFS 'all_squash' option to work. For example, in my host OS,the UID and GID for my user is 1000, while that of vagrant's in the guest OS is 1001. I am not sure what's the right way to fix it. Use some provisioning scripts to configure the box on the fly? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/110> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

7 years, 6 months

1
1
0 / 0

[cloud] #81: Create cloud training materials for ambassadors

by Fedora Cloud Trac Tickets

#81: Create cloud training materials for ambassadors -------------------------------------------+----------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 22 Component: Collaboration & Communication | Keywords: -------------------------------------------+----------------------- Many Fedora Ambassadors come from a desktop or old-school sysadmin background. Cloudy concepts are new and foreign. In talking with some of them, it was suggested that it'd be really, really helpful to have some basic training materials for our own ambassadors -- what is cloud, why does it matter, what is Fedora Cloud, what is our strategy, why do _we_ matter, and so on. http://mattdm.org/fedora/cloud2013/#1 might be a starting point. Maybe some more interactive training would even be useful. Of course, it'd also be awesome to get some people from the new modern world interested in being ambassadors as well -- another direction to approach the same issue. (But even then, training on what _we_ are doing would be useful.) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/81> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

7 years, 6 months

2
3
0 / 0

[cloud] #38: Automatic Smoketests on Image Build

by Fedora Cloud Trac Tickets

#38: Automatic Smoketests on Image Build --------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Testing & QA | Keywords: --------------------------+------------------------------- '''Summary:''' When a new image is built in Koji, automatically boot it and run a basic matrix of tests. '''Importance:''' moderate (worst case, we can keep doing this by hand) '''Timeframe:''' F21 alpha / Want to reduce manual test workload '''Fedora Sub-Project/SIG:''' QA and the Taskotran project '''Cloud SIG owner:''' Sandro Mathys https://fedoraproject.org/wiki/Taskotron -- Ticket URL: <https://fedorahosted.org/cloud/ticket/38> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

7 years, 6 months

1
6
0 / 0

[cloud] #25: File F21 change: OpenShift Out-of-the-Box Image

by Nobody

#25: File F21 change: OpenShift Out-of-the-Box Image --------------------------------+------------------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Feature Deadline) Component: OpenShift Origin | Keywords: Image | --------------------------------+------------------------------------------ '''Summary:''' Fedora Cloud agreed to make a base image plus several tailored to specific purposes. This is one of the tailored ones — OpenShift ready to run. '''Importance:''' nice to have (if we fail to do it, we are not any worse- off than we are now, and OpenShift can still be installed on the base iamge.) '''Timeframe:''' F21 alpha / If it's not ready for alpha, we have missed this release '''Scope:''' self-contained (in collaboration with OpenShift developers) '''Cloud SIG owner:''' TBD https://fedoraproject.org/wiki/Changes/OpenShift_Out-of-the- Box_Cloud_Image -- Ticket URL: <https://fedorahosted.org/cloud/ticket/25> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

7 years, 6 months

2
2
0 / 0

[cloud] #28: discuss modularized SELinux policy packaging

by Nobody

#28: discuss modularized SELinux policy packaging ------------------------------+----------------------- Reporter: mattdm | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Fedora 22 Component: Cloud Base Image | Keywords: ------------------------------+----------------------- Possible F22 feature? Summary: Monolith SELinux policy has rules for everything that could exist, not just that which is installed. Possible room for reduction here. '''Importance:''' nice-to-have '''Timeframe:''' F21 or F22 / This is not low-hanging fruit. '''Scope:''' self-contained (SELinux) ''' Cloud SIG owner:''' TBD (No Feature filed at this time -- discuss with SELinux policy maintainers) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/28> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

7 years, 6 months

2
1
0 / 0

[cloud] #73: test cases for cloud-init

by Fedora Cloud Trac Tickets

#73: test cases for cloud-init --------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Final) Component: Testing & QA | Keywords: --------------------------+------------------------------- We have a number of bugs for #cloud-config syntax not working properly -- probably because it's mostly been tested with debian/ubuntu-universe tools. For example: * https://bugzilla.redhat.com/show_bug.cgi?id=1126857 * https://bugzilla.redhat.com/show_bug.cgi?id=1126365 We should fix these, obviously, but also, each time we fix one, we should make a test case -- ideally an automatic test case! -- to make sure it stays fixed. It would also be nice to have some other test cases for cloud-config syntax we expect to work. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/73> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

7 years, 6 months

1
1
0 / 0

[cloud] #57: get official images uploaded into Rackspace

by Fedora Cloud Trac Tickets

#57: get official images uploaded into Rackspace -------------------------------------------------+------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 Component: Infrastructure & Release | (Final) Engineering | Keywords: -------------------------------------------------+------------------------- Work with Rackspace engineers... they don't yet have public image sharing, but getting our official images uploaded to a fedora account as part of the release process would be a good start. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/57> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

7 years, 6 months

1
1
0 / 0

[cloud] #42: policies for batched updates

by Fedora Cloud Trac Tickets

#42: policies for batched updates ------------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Final) Component: Software Updates | Keywords: ------------------------------+------------------------------- See ticket #18 We want to putting out updated images periodically (or aperiodically as needed). What are the rules? What are the procedures? Where are they documented? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/42> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

7 years, 6 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud September 2016