ANNOUNCE: Oz 0.11.0 release
by Chris Lalancette
All,
I'm pleased to announce release 0.11.0 of Oz. Oz is a program
for doing automated installation of guest operating systems with
limited input from the user. Release 0.11.0 is a bugfix and feature
release for Oz. Some of the highlights between Oz 0.10.0 and 0.11.0
are:
* Add support for installing Ubuntu 13.04
* Add the ability to get user-specific ICICLE information
* Add the ability to generate ICICLE safely, by using a disk snapshot
* Add the ability to include extra files and directories on the installation ISO
* Add the ability to install to alternate file types, like qcow2, etc.
* Add support for installing Ubuntu 5.04/5.10
* Add support for installing Fedora 19
* Add support for installing Debian 7
* Add support for Windows 2012 and 8
* Add support for getting files over http for the commands/files
section of the TDL
* Add support for setting a custom MAC address to guests during installation
* Add support for user specified disk and NIC model
* Add support for OpenSUSE 12.3
* Add support for URL based installs for Ubuntu
A tarball and zipfile of this release is available on the Github
releases page: https://github.com/clalancette/oz/releases . Packages
for Fedora-18 and Fedora-19 have been built in Koji and will
eventually make their way to stable. Instructions on how to get and
use Oz are available at http://github.com/clalancette/oz/wiki .
If you have questions or comments about Oz, please feel free to
contact me at clalancette at gmail.com, or open up an issue on the
github page: http://github.com/clalancette/oz/issues .
This was one of the most active Oz releases ever, because of the
feedback and patches from the community. Thanks to everyone who
contributed to this release through bug reports, patches, and
suggestions for improvement.
Chris Lalancette
10 years, 9 months
Fedora Cloud Guide
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
With increasing development and interest in using Fedora in the cloud,
updating the Fedora cloud guide[1] seems like a good idea. Some interest
in working on the guide has developed since Matthew mentioned it on the
docs list[2]; I'd like to learn more about Fedora in the cloud and
improve the documentation along the way, and a couple people have
expressed the same to me out-of-band.
There's a roadblock to improving the Guide expeditiously, however. We're
not immediately familiar with the subject matter, and I'm not sure how
much mileage we can get out of available resources ( ie the free EC2
instance).
I'm hoping a conversation with the Cloud SIG can point us in the right
direction. Off the top of my head, I think we could use:
- - a review of the current guide for deprecated and missing content
- - an updated outline for new content for the writers to research and
flesh out
- - suggestions for how to test and validate our writing without getting
too much out of pocket
- - open communication with the Cloud SIG - or at least a reluctant
point of contact for when we get stuck :)
Of course, ideas for improvement of any kind are welcome.
[1]
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/C...
[2] https://lists.fedoraproject.org/pipermail/docs/2013-July/015101.html
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJR6uCCAAoJEL1wZM0+jj2ZAvgH/1zzvSGn7LV16QKFm19DL2/t
UqDdRP44Uztn6hwk3GzP0/dVVdsSFtBIlPL+SZDrjMsYtqOfgW9Hzxc+dhSTb53e
27YM629VBMU/Lw+aQj7cSOy56cnzPSBzfSHnZdsYo5rVWbKrRUVILYv847F6Ppsv
YJLOl4y+78SpL+79QHTWXVsARSfVr+8AvzSnT+ek3nwUcqKS8VxTKHMxFV58DVyZ
PRtA9fGNyRKubzU6SEhKx+dFCx/+wMBNDAVJee36HAvi8eBGl5WmsK5AMlwcJ8L2
BPlSp00hLGerbISOjpICPLRlAQlZW61lcbEa84sX2IbUbC4XLc260hBV1x1rRHM=
=w89+
-----END PGP SIGNATURE-----
10 years, 10 months
CfP 8th Workshop on Virtualization in High-Performance Cloud Computing (VHPC '13)
by VHPC 15
we apologize if you receive multiple copies of this CfP
=================================================================
CALL FOR PAPERS
8th Workshop on Virtualization in High-Performance Cloud Computing (VHPC '13)
as part of SC 13, Denver, Colorado | sponsored by ACM sighpc
=================================================================
Date: November 22, 2013
Workshop URL: http://vhpc.org
Paper Submission Deadline: September 23, 2013
CALL FOR PAPERS
Virtualization has become a common abstraction layer in modern data
centers, enabling resource owners to manage complex infrastructures
independently of their applications. Conjointly, virtualization is becoming
a driving technology for a manifold of industry grade IT services. The
cloud concept includes the notion of a separation between resource
owners and users, adding services such as hosted application
frameworks and queueing. Utilizing the same infrastructure, clouds
carry significant potential for use in cpu-intensive or data-intensive
computing. The ability of clouds to provide for requests and releases
of vast computing resources dynamically and close to the marginal
cost of providing the services is unprecedented in the history of
scientific and commercial computing.
This workshop aims to bring together industrial providers with the
application community in order to foster discussion, collaboration
and mutual exchange of knowledge and experience.
The workshop will be one day in length, composed of 20 min paper
presentations, each followed by 10 min discussion sections. Lightning
talks are limited to 5 minutes. Presentations may be accompanied by
interactive demonstrations.
TOPICS
Topics of interest include, but are not limited to:
- Management, deployment and monitoring of VM-based environments
- VM-cloud performance monitoring
- VM cloud topology management and optimization
- Operating systems virtualization supportpptimization
- VM-based cloud performance modelling
- Network virtualization for VM-environments
- Data virtualization
- Cloudbursting
- Evolved grid architectures including such based on network virtualization
- Workload characterization for VM-based environments
- Optimized communication libraries/protocols in the cloud
- System and process/bytecode VM convergence
- Cloud frameworks and APIs
- GPU Virtualization architectures and APIs
- Checkpointing/migration of large compute jobs
- Instrumentation interfaces and languages
- VMM performance (auto-)tuning on various load types
- Cloud reliability, fault-tolerance, and security
- Heterogeneous virtualized environments
- Paravirtualized I/O
- Services in cloud HPC
- Research and education use cases
- Virtualization in cloud, cluster and grid environments
- Cross-layer VM optimizations
- Cloud HPC use cases including optimizations
- Energy-aware virtualization
- Performance and cost modelling
- QoS and and service levels
- Languages for describing highly-distributed compute jobs
- VM cloud and cluster distribution algorithms, load balancing
- Instrumentation interfaces and languages
- Hypervisor extensions and tools for cluster and grid computing
- Virtual machine monitor platforms
- Cluster provisioning in the cloud
Important Dates:
Rolling Paper registration
September 23, 2013 - Full paper submission
October 21, 2013 - Acceptance notification
November 8, 2013 - Camera-ready version due
Lightning Talks:
August 9, 2013 - Deadline for lightning talk abstracts
September 2, 2013 - Lightning talk notification
November 22, 2013 - Workshop Date
TPC
CHAIR
Michael Alexander (chair), TU Wien, Austria
Gianluigi Zanetti (co-chair), CRS4, Italy
Anastassios Nanos (co-chair), NTUA, Greece
PROGRAM COMMITTEE
Costas Bekas, IBM, Switzerland
Jakob Blomer, CERN
Giovanni Busonera, CRS4, Italy
Roberto Canonico, University of Napoli Federico II, Italy
Simon Crosby, Bromium, USA
Tommaso Cucinotta, Alcatel-Lucent Bell Labs, Ireland
Michael Day, IBM, USA
Casimer DeCusatis, IBM, USA
William Gardner, University of Guelph, USA
Marcus Hardt, Forschungszentrum Karlsruhe, Germany
Sverre Jarp, CERN, Switzerland
Xuxian Jiang, NC State, USA
Krishna Kant, George Mason University, USA
Romeo Kinzler, IBM, Switzerland
Nectarios Koziris, National Technical University of Athens, Greece
Simone Leo, CRS4, Italy
Jean-Marc Menaud, Ecole des Mines de Nantes, France
Dimitrios Nikolopoulos, Queen's University of Belfast, UK
Josh Simons, VMWare, USA
Borja Sotomayor, University of Chicago, USA
Yoshio Turner, HP Labs, USA
Kurt Tutschku, Blekinge Institute of Technology, Sweden
Chao-Tung Yang, Tunghai University, Taiwan
PAPER SUBMISSION-PUBLICATION
Papers submitted to the workshop will be reviewed by at least two
members of the program committee and external reviewers. Submissions
should include abstract, key words, the e-mail address of the
corresponding author, and must not exceed 8 pages, including tables
and figures at a main font size no smaller than 11 point. Submission
of a paper should be regarded as a commitment that, should the paper
be accepted, at least one of the authors will register and attend the
conference to present the work.
Accepted papers will be published in the ACM International Conference
Proceedings Series. The format must be according to the ACM SIG style.
Initial submissions are in PDF; authors of accepted papers will be
requested to provide source files.
Format Guidelines:
http://www.acm.org/sigs/publications/sigguide-v2.2sp
Style template:
http://www.acm.org/sigs/publications/proceedings-templates
Abstract Submission Link:
http://edas.info/newPaper.php?c=14791
LIGHTNING TALKS
Lightning Talks are non-paper track synoptical in nature that are strictly
limited to 5 minutes. They can be used to gain early feedback on ongoing
research, for demonstrations, to present research results, early research
ideas, perspectives and positions of interest to the community.
GENERAL INFORMATION
The workshop will be held as part of SC’13, Denver, Colorado.
SC 2013: http://sc13.supercomputing.org/
10 years, 10 months
Best way to assemble vm images
by Krishna Raman
Hi,
When building on a f19 system, is appliance-creator still the best way to build F19 qcow2
images or should I be using something else?
I am running into quite a few bugs in the latest version of appliance-creator on F19 and am
curious what is being used to build the official Fedora cloud images.
Thanks
Krishna
10 years, 10 months
Persistent URLs for Fedora Cloud images
by Kashyap Chamarthy
Heya,
I know Matt is working to get Fedora cloud images in shape.
It'd be nice to have Fedora Cloud image URLs be persistent (if they change, maybe symlinks
can be created?)
For instance, OpenStack's diskimage-builder hard codes[1] path to Fedora 18 images
-----
[...]
DIB_CLOUD_IMAGES=${DIB_CLOUD_IMAGES:-http://mattdm.fedorapeople.org/cloud...
DIB_RELEASE=${DIB_RELEASE:-Fedora18}
BASE_IMAGE_FILE=${BASE_IMAGE_FILE:-$DIB_RELEASE-Cloud-$ARCH-latest.qcow2}
BASE_IMAGE_TAR=$DIB_RELEASE-Cloud-$ARCH-latest.tgz
echo "Fetching Base Image"
$TMP_HOOKS_PATH/bin/cache-url $DIB_CLOUD_IMAGES/$BASE_IMAGE_FILE $IMG_PATH/$BASE_IMAGE_FILE
[...]
-----
And, now it throws an HTTP 302 response from the server while trying to fetch either F18
or F19 images, although the absolute path to F18 qcow2 image is available via wget.
Something has changed on the server.
Can we please try to make these URLs persistent?
Thanks.
~~~~~~
[1]
https://github.com/stackforge/diskimage-builder/blob/master/elements/fedo...
--
/kashyap
10 years, 10 months
Growpart support in fedora images
by Krishna Raman
Hi,
Looks like the latest cloud images provide only a 2GB root partition as opposed to 10Gb which was the earlier size.
What is the best way to resize/grow the root FS on ec2? Can I use something in cloud-init to do this?
Thanks
Krishna
10 years, 10 months
Re: Persistent URLs for Fedora Cloud images
by Kashyap Chamarthy
On 07/09/2013 04:11 PM, Lucas Alvares Gomes wrote:
> Would be cool as well to have a persistent file name for the last image created, e.g Fedora-x86_64-19-latest-sda.qcow2
Just before I sent my email, Matthew Miller sent an email with these short URLs:
(Only qcow2 for now)
======
These links all work now:
http://cloud.fedoraproject.org/fedora-19.x86_64.qcow2
http://cloud.fedoraproject.org/fedora-19.i386.qcow2
http://cloud.fedoraproject.org/fedora-latest.i386.qcow2
http://cloud.fedoraproject.org/fedora-latest.x86_64.qcow2
(They will redirect to a mirror link provided by mirrormanager.)
======
>
> Cheers,
> Lucas
>
> ----- Original Message -----
>> From: "Kashyap Chamarthy" <kchamart(a)redhat.com>
>> To: "Fedora Cloud SIG" <cloud(a)lists.fedoraproject.org>, "Matthew Miller" <mattdm(a)fedoraproject.org>
>> Cc: "Lucas Alvares Gomes Martins" <lmartins(a)redhat.com>
>> Sent: Tuesday, July 9, 2013 10:27:12 AM
>> Subject: Persistent URLs for Fedora Cloud images
>>
>> Heya,
>>
>>
>> I know Matt is working to get Fedora cloud images in shape.
>>
>> It'd be nice to have Fedora Cloud image URLs be persistent (if they change,
>> maybe symlinks
>> can be created?)
>>
>> For instance, OpenStack's diskimage-builder hard codes[1] path to Fedora 18
>> images
>>
>> -----
>> [...]
>> DIB_CLOUD_IMAGES=${DIB_CLOUD_IMAGES:-http://mattdm.fedorapeople.org/cloud...
>> DIB_RELEASE=${DIB_RELEASE:-Fedora18}
>> BASE_IMAGE_FILE=${BASE_IMAGE_FILE:-$DIB_RELEASE-Cloud-$ARCH-latest.qcow2}
>> BASE_IMAGE_TAR=$DIB_RELEASE-Cloud-$ARCH-latest.tgz
>>
>> echo "Fetching Base Image"
>> $TMP_HOOKS_PATH/bin/cache-url $DIB_CLOUD_IMAGES/$BASE_IMAGE_FILE
>> $IMG_PATH/$BASE_IMAGE_FILE
>> [...]
>> -----
>>
>> And, now it throws an HTTP 302 response from the server while trying to fetch
>> either F18
>> or F19 images, although the absolute path to F18 qcow2 image is available via
>> wget.
>>
>> Something has changed on the server.
>>
>> Can we please try to make these URLs persistent?
>>
>> Thanks.
>>
>> ~~~~~~
>> [1]
>> https://github.com/stackforge/diskimage-builder/blob/master/elements/fedo...
>>
>>
>>
>> --
>> /kashyap
>>
>
>
--
/kashyap
10 years, 10 months
generic/fedora-20-i386-cloud.ks generic/fedora-20-i386.ks generic/fedora-20-i386-minimal.ks generic/fedora-20-x86_64-cloud.ks generic/fedora-20-x86_64.ks generic/fedora-20-x86_64-minimal.ks
by Matthew Miller
generic/fedora-20-i386-cloud.ks | 3 +++
generic/fedora-20-i386-minimal.ks | 3 +++
generic/fedora-20-i386.ks | 3 +++
generic/fedora-20-x86_64-cloud.ks | 3 +++
generic/fedora-20-x86_64-minimal.ks | 3 +++
generic/fedora-20-x86_64.ks | 3 +++
6 files changed, 18 insertions(+)
New commits:
commit a5f27b0daaff1f21448222342d539a7b57173456
Author: Matthew Miller <mattdm(a)mattdm.org>
Date: Fri Jul 5 10:06:02 2013 -0400
remove /var/lib/random-seed so it's not the same in every image
diff --git a/generic/fedora-20-i386-cloud.ks b/generic/fedora-20-i386-cloud.ks
index 30c60eb..2312230 100644
--- a/generic/fedora-20-i386-cloud.ks
+++ b/generic/fedora-20-i386-cloud.ks
@@ -224,6 +224,9 @@ fi
# change will be in an upcoming cloud-init update
sed -i 's/ec2-user/fedora/;s/EC2 user/Fedora Cloud User/' /etc/cloud/cloud.cfg
+echo "Removing random-seed so it's not the same in every image."
+rm -f /var/lib/random-seed
+
echo "Cleaning old yum repodata."
yum clean all
truncate -c -s 0 /var/log/yum.log
diff --git a/generic/fedora-20-i386-minimal.ks b/generic/fedora-20-i386-minimal.ks
index b2cd8e7..7ff7d58 100644
--- a/generic/fedora-20-i386-minimal.ks
+++ b/generic/fedora-20-i386-minimal.ks
@@ -191,6 +191,9 @@ fi
# make sure firstboot doesn't start
echo "RUN_FIRSTBOOT=NO" > /etc/sysconfig/firstboot
+echo "Removing random-seed so it's not the same in every image."
+rm -f /var/lib/random-seed
+
echo "Cleaning old yum repodata."
yum clean all
truncate -c -s 0 /var/log/yum.log
diff --git a/generic/fedora-20-i386.ks b/generic/fedora-20-i386.ks
index 4071f85..29ae9c4 100644
--- a/generic/fedora-20-i386.ks
+++ b/generic/fedora-20-i386.ks
@@ -183,6 +183,9 @@ fi
# make sure firstboot doesn't start
echo "RUN_FIRSTBOOT=NO" > /etc/sysconfig/firstboot
+echo "Removing random-seed so it's not the same in every image."
+rm -f /var/lib/random-seed
+
echo "Cleaning old yum repodata."
yum clean all
truncate -c -s 0 /var/log/yum.log
diff --git a/generic/fedora-20-x86_64-cloud.ks b/generic/fedora-20-x86_64-cloud.ks
index 1e2512f..f75ee4a 100644
--- a/generic/fedora-20-x86_64-cloud.ks
+++ b/generic/fedora-20-x86_64-cloud.ks
@@ -221,6 +221,9 @@ fi
# change will be in an upcoming cloud-init update
sed -i 's/ec2-user/fedora/;s/EC2 user/Fedora Cloud User/' /etc/cloud/cloud.cfg
+echo "Removing random-seed so it's not the same in every image."
+rm -f /var/lib/random-seed
+
echo "Cleaning old yum repodata."
yum clean all
truncate -c -s 0 /var/log/yum.log
diff --git a/generic/fedora-20-x86_64-minimal.ks b/generic/fedora-20-x86_64-minimal.ks
index 3f64ec5..e625acb 100644
--- a/generic/fedora-20-x86_64-minimal.ks
+++ b/generic/fedora-20-x86_64-minimal.ks
@@ -189,6 +189,9 @@ fi
# make sure firstboot doesn't start
echo "RUN_FIRSTBOOT=NO" > /etc/sysconfig/firstboot
+echo "Removing random-seed so it's not the same in every image."
+rm -f /var/lib/random-seed
+
echo "Cleaning old yum repodata."
yum clean all
truncate -c -s 0 /var/log/yum.log
diff --git a/generic/fedora-20-x86_64.ks b/generic/fedora-20-x86_64.ks
index 0f5799d..bb8d889 100644
--- a/generic/fedora-20-x86_64.ks
+++ b/generic/fedora-20-x86_64.ks
@@ -181,6 +181,9 @@ fi
# make sure firstboot doesn't start
echo "RUN_FIRSTBOOT=NO" > /etc/sysconfig/firstboot
+echo "Removing random-seed so it's not the same in every image."
+rm -f /var/lib/random-seed
+
echo "Cleaning old yum repodata."
yum clean all
truncate -c -s 0 /var/log/yum.log
10 years, 10 months
