keystone or dashboard problem?
by Vogel Nicolas
Hi,
I've just made a new install with the latest version of the < RedHat getting started guide with Openstack Folsom > Revision 1.0-2.
I'm using CentOS 6.3 for this install.
After installing Openstack-keystone, I'm unable to perform "keystone user-list" and "keystone token-get". I have sourced the keystonerc_username file but the system says "Expecting an endpoint provided via either --endpoint or env[SERVICE_ENDPOINT]". When I'm explicitly given the endpoint in the command line, the output is "Configuration error: Client configured to run without a service catalog. Run the client using --os-auth-url or OS_AUTH_URL, instead of --os-endpoint or OS_SERVICE_ENDPOINT, for example."
But the OS_AUTH_URL is configured in my keystonerc_username file so I don't understand why the system asks for it.
I can then all the installation steps without problems, but after I given my credentials in the dashboard login page (admin/secret or username/secret), I got "Internal Server Error".
Is that linked with the first problem from Keystone?
I'm searching for more information in logs but currently I found no answer to my questions.
Thanks for help,
Nicolas.
10 years, 7 months
fedora cloud images (non ec2 providers)
by Giulio Fidente
hi all,
in recent times I found myself (as also other people) on the lookout for
some 'official' fedora cloud images
people on #fedora-cloud pointed me at:
http://mattdm.fedorapeople.org/cloud-images/
those worked quite well for me and, when they didn't, I just built some
using Oz
I was wondering if there is any work ongoing to announce those more
officially or if any help is wanted to rebuild/maintain some more images
I'd be happy to help with that, but I'm not sure what would be the best
approach to it
Please excuse me if the topic has been discussed already but I've only
joined the mailing list in recent times.
--
Giulio Fidente
IRC: giulivo
10 years, 7 months
Re: cloud Digest, Vol 38, Issue 21
by Steve Loranz
Imagefactory is more than a REST interface to oz. Oz creates a JEOS image. The customization that oz performs is limited to installing additional packages or running commands within a VM started with the JEOS image. Oz does not have knowledge of what needs to be added or how an image needs to be translated for a specific virtualization platform or cloud target. This is what imgfac brings to the party.
I really wish we could get past the notion that imagefactory is just a REST interface to oz. What are we doing wrong on imgfac.org that leads people to see imagefactory this way? Maybe I should be happy about this, because it means we're doing a good job of hiding what is needed to go from base image to provider image for cloud targets like EC2 and vSphere.
-steve
On Feb 27, 2013, at 6:00 AM, cloud-request(a)lists.fedoraproject.org wrote:
> ------------------------------
>
> Message: 5
> Date: Wed, 27 Feb 2013 12:06:19 +0100
> From: Giulio Fidente <gfidente(a)fedoraproject.org>
> To: Fedora Cloud SIG <cloud(a)lists.fedoraproject.org>
> Subject: Re: fedora cloud images (non ec2 providers)
> Message-ID: <512DE8AB.6060909(a)fedoraproject.org>
> Content-Type: text/plain; charset=UTF-8
>
> On 02/26/2013 08:40 PM, Matthew Miller wrote:
>> On Mon, Feb 25, 2013 at 06:05:45PM +0100, Giulio Fidente wrote:
>>> I was wondering if there is any work ongoing to announce those more
>>> officially or if any help is wanted to rebuild/maintain some more images
>>
>> Hi Giulio. I'm glad you found those images helpful. There *is* a plan to
>> make more-official images for Fedora 19, and you can see that at
>> http://fedoraproject.org/wiki/Features/FirstClassCloudImages. A lot of this
>> is internal infrastructure work, but I'm sure we can find some way to fit in
>> your skills.
>
> I like the plan a lot, it looks like the major issue now is the
> integration of imgfac/oz with koji
>
> I happen to have worked with imgfac and know decently its REST interface
> but, for the scope of this project, can't we just stick to Oz?
>
> I don't think imgfac would add much to the process while it will instead
> prevent us from passing customized kickstarts to Oz
>
> this said, I think I could help with koji... who should I ping?
>
>> You may also be interested in
>> http://git.fedorahosted.org/cgit/cloud-kickstarts.git/tree/generic, which is
>> the source repository for the kickstart files from which the image is
>> generated. Any improvements/suggestions/patches are welcome.
>
> would it be worth trying some ARM build?
> --
> Giulio Fidente
> IRC: giulivo
10 years, 7 months
Handling differences between EPEL and Fedora
by Juerg Haefliger
All,
I'm in the process of building the dracut package that goes along with
cloud-utils. I need to install different files for Fedora vs. EPEL
(due to the different versions of dracut). How is this best handled?
Can I just key off of a macro in the spec file?
%if fedora <-- What goes here?
cp A B C
%else
cp X Y C
%endif
Or do I need to check for the dracut version somehow? If so, how can
this be accomplished at package build time?
Thanks
...Juerg
10 years, 7 months
[PATCH] add a PTY console; & use a UNIX domain socket for better security
by Kashyap Chamarthy
A couple of small additions:
- Add a PTY serial console, so that "virsh console foo" works out of the box
(once the guest is installed).
- Use a UNIX domain socket server (for better security) as a character
device instead of a TCP port.
Thanks to Dan Berrange for suggesting to use UNIX domain socket.
---
oz/Guest.py | 20 +++++++++-----------
1 files changed, 9 insertions(+), 11 deletions(-)
diff --git a/oz/Guest.py b/oz/Guest.py
index 1cd106e8abc5fcb3ff155c0d11f93bf20c58ac3a..2725f672e42a8f547040c2b52b3e78262e58c105 100644
--- a/oz/Guest.py
+++ b/oz/Guest.py
@@ -419,20 +419,18 @@ class Guest(object):
elif self.mousetype == "usb":
inputdev.setProp("type", "tablet")
inputdev.setProp("bus", "usb")
- # console
- console = devices.newChild(None, "console", None)
- console.setProp("type", "pty")
- consoleTarget = console.newChild(None, "target", None)
- consoleTarget.setProp("port", "0")
- # serial
+ # Serial console pseudo TTY
serial = devices.newChild(None, "serial", None)
- serial.setProp("type", "tcp")
+ serial.setProp("type", "pty")
+ serialTarget = serial.newChild(None, "target", None)
+ serialTarget.setProp("port", "0")
+ # Use a UNIX domain socket as character device
+ serial = devices.newChild(None, "serial", None)
+ serial.setProp("type", "unix")
serialSource = serial.newChild(None, "source", None)
serialSource.setProp("mode", "bind")
- serialSource.setProp("host", "127.0.0.1")
- serialSource.setProp("service", str(self.listen_port))
- serialProtocol = serial.newChild(None, "protocol", None)
- serialProtocol.setProp("type", "raw")
+ sockname = tempfile.mktemp(prefix="/var/tmp/oz-")
+ serialSource.setProp("path", sockname)
serialTarget = serial.newChild(None, "target", None)
serialTarget.setProp("port", "1")
# boot disk
--
1.7.7.6
10 years, 7 months
[PATCH] Add the serial conole atrribute in kickstart files for Fedora 14-18
by Kashyap Chamarthy
A simple patch to add serial console attribute to kickstart files Fedora
{14,15,16,17,18}. Although, kickstart files for RHEL and Fedora releases prior
to Fedora-14 had the serial console attribute added. So I guess, it's a minor
over look.
---
oz/auto/fedora-14-jeos.ks | 2 +-
oz/auto/fedora-15-jeos.ks | 2 +-
oz/auto/fedora-16-jeos.ks | 2 +-
oz/auto/fedora-17-jeos.ks | 2 +-
oz/auto/fedora-18-jeos.ks | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/oz/auto/fedora-14-jeos.ks b/oz/auto/fedora-14-jeos.ks
index fd2b5ea876b23cd23052e66d761d0dd7ba4f9eed..dd534c600e21fc986ea1c72e9300b9fb1154643e 100644
--- a/oz/auto/fedora-14-jeos.ks
+++ b/oz/auto/fedora-14-jeos.ks
@@ -9,7 +9,7 @@ firewall --disabled
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone --utc America/New_York
-bootloader --location=mbr
+bootloader --location=mbr --append="console=tty0 console=ttyS0,115200"
zerombr
clearpart --all --drives=vda
diff --git a/oz/auto/fedora-15-jeos.ks b/oz/auto/fedora-15-jeos.ks
index fd2b5ea876b23cd23052e66d761d0dd7ba4f9eed..dd534c600e21fc986ea1c72e9300b9fb1154643e 100644
--- a/oz/auto/fedora-15-jeos.ks
+++ b/oz/auto/fedora-15-jeos.ks
@@ -9,7 +9,7 @@ firewall --disabled
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone --utc America/New_York
-bootloader --location=mbr
+bootloader --location=mbr --append="console=tty0 console=ttyS0,115200"
zerombr
clearpart --all --drives=vda
diff --git a/oz/auto/fedora-16-jeos.ks b/oz/auto/fedora-16-jeos.ks
index d1290ecded73cb3ffedc7fdaa54ae0e9b8412947..ebcbfe178f9e5f6db94330b62d5abf58b7fceb14 100644
--- a/oz/auto/fedora-16-jeos.ks
+++ b/oz/auto/fedora-16-jeos.ks
@@ -9,7 +9,7 @@ firewall --disabled
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone --utc America/New_York
-bootloader --location=mbr
+bootloader --location=mbr --append="console=tty0 console=ttyS0,115200"
zerombr
clearpart --all --drives=vda
diff --git a/oz/auto/fedora-17-jeos.ks b/oz/auto/fedora-17-jeos.ks
index 19b5f288c063e129cf0fd480df52f4a9be89f920..2a8b0f3736010d5c038d0be27fdcd8a67c0f7eb2 100644
--- a/oz/auto/fedora-17-jeos.ks
+++ b/oz/auto/fedora-17-jeos.ks
@@ -9,7 +9,7 @@ firewall --disabled
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone --utc America/New_York
-bootloader --location=mbr
+bootloader --location=mbr --append="console=tty0 console=ttyS0,115200"
zerombr
clearpart --all --drives=vda
diff --git a/oz/auto/fedora-18-jeos.ks b/oz/auto/fedora-18-jeos.ks
index e62399a4a65f43c0518e2d101e48f79aeeb0651e..e19960078fcc0b1bb24908f32f3c559a521103a9 100644
--- a/oz/auto/fedora-18-jeos.ks
+++ b/oz/auto/fedora-18-jeos.ks
@@ -9,7 +9,7 @@ firewall --disabled
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone --utc America/New_York
-bootloader --location=mbr
+bootloader --location=mbr --append="console=tty0 console=ttyS0,115200"
zerombr
clearpart --all --drives=vda
--
1.7.7.6
10 years, 7 months
Keystone on Rawhide tracebacks around sqlalchemy
by Pete Zaitcev
Greetings:
When I try to run Keystone, it blows up with this:
File "/usr/lib/python2.7/site-packages/migrate/versioning/schema.py", line 10, in <module>
from sqlalchemy import exceptions as sa_exceptions
ImportError: cannot import name exceptions
python-sqlalchemy-0.8.0-0.1.b1.fc19.x86_64
openstack-keystone-2013.1-0.2.g2.fc19.noarch
Weird thing is, I'm not trying to migrate anything anywhere.
Just launching a new Keystone with "keystone-manage db_sync".
Does it work for anyone else?
Thanks,
-- Pete
10 years, 7 months
AWS tools for Fedora
by Danishka Navin
Hi,
I am using Fedora 18, and I am using AWS services directly login to the aws
console.
I did a yum search for aws tools for Fedora but no luck.
Highly appreciate if some help me to setup.
10 years, 7 months
ec2/fedora-18-i386-ec2.ks ec2/fedora-18-x86_64-ec2.ks generic/fedora-18-i386-cloud.ks generic/fedora-18-i386.ks generic/fedora-18-i386-minimal.ks generic/fedora-18-x86_64-cloud.ks generic/fedora-18-x86_64.ks generic/fedora-18-x86_64-minimal.ks
by Matthew Miller
ec2/fedora-18-i386-ec2.ks | 13 +++++++++++++
ec2/fedora-18-x86_64-ec2.ks | 13 +++++++++++++
generic/fedora-18-i386-cloud.ks | 13 +++++++++++++
generic/fedora-18-i386-minimal.ks | 13 +++++++++++++
generic/fedora-18-i386.ks | 13 +++++++++++++
generic/fedora-18-x86_64-cloud.ks | 13 +++++++++++++
generic/fedora-18-x86_64-minimal.ks | 13 +++++++++++++
generic/fedora-18-x86_64.ks | 13 +++++++++++++
8 files changed, 104 insertions(+)
New commits:
commit 7c1fa7d04380be00b2dfe4d2e6a4ef9180367259
Author: Matthew Miller <mattdm(a)mattdm.org>
Date: Fri Jan 18 13:58:46 2013 -0600
Appliance-tools doesn't create the sysconfig kernel file, and without that,
new kernels don't become the default
diff --git a/ec2/fedora-18-i386-ec2.ks b/ec2/fedora-18-i386-ec2.ks
index 5ff8d5b..41d607e 100644
--- a/ec2/fedora-18-i386-ec2.ks
+++ b/ec2/fedora-18-i386-ec2.ks
@@ -136,6 +136,19 @@ echo .
echo "Disabling tmpfs for /tmp."
systemctl mask tmp.mount
+# appliance-creator does not make this important file.
+if [ ! -e /etc/sysconfig/kernel ]; then
+echo "Creating /etc/sysconfig/kernel."
+cat <<EOF > /etc/sysconfig/kernel
+# UPDATEDEFAULT specifies if new-kernel-pkg should make
+# new kernels the default
+UPDATEDEFAULT=yes
+
+# DEFAULTKERNEL specifies the default kernel package type
+DEFAULTKERNEL=kernel-PAE
+EOF
+fi
+
# Uncomment this if you want to use cloud init but suppress the creation
# of an "ec2-user" account. This will, in the absence of further config,
# cause the ssh key from a metadata source to be put in the root account.
diff --git a/ec2/fedora-18-x86_64-ec2.ks b/ec2/fedora-18-x86_64-ec2.ks
index 72bfcf9..3250fd4 100644
--- a/ec2/fedora-18-x86_64-ec2.ks
+++ b/ec2/fedora-18-x86_64-ec2.ks
@@ -136,6 +136,19 @@ echo .
echo "Disabling tmpfs for /tmp."
systemctl mask tmp.mount
+# appliance-creator does not make this important file.
+if [ ! -e /etc/sysconfig/kernel ]; then
+echo "Creating /etc/sysconfig/kernel."
+cat <<EOF > /etc/sysconfig/kernel
+# UPDATEDEFAULT specifies if new-kernel-pkg should make
+# new kernels the default
+UPDATEDEFAULT=yes
+
+# DEFAULTKERNEL specifies the default kernel package type
+DEFAULTKERNEL=kernel
+EOF
+fi
+
# Uncomment this if you want to use cloud init but suppress the creation
# of an "ec2-user" account. This will, in the absence of further config,
# cause the ssh key from a metadata source to be put in the root account.
diff --git a/generic/fedora-18-i386-cloud.ks b/generic/fedora-18-i386-cloud.ks
index 8e7ef60..bf04d8b 100644
--- a/generic/fedora-18-i386-cloud.ks
+++ b/generic/fedora-18-i386-cloud.ks
@@ -139,6 +139,19 @@ echo .
echo "Disabling tmpfs for /tmp."
systemctl mask tmp.mount
+# appliance-creator does not make this important file.
+if [ ! -e /etc/sysconfig/kernel ]; then
+echo "Creating /etc/sysconfig/kernel."
+cat <<EOF > /etc/sysconfig/kernel
+# UPDATEDEFAULT specifies if new-kernel-pkg should make
+# new kernels the default
+UPDATEDEFAULT=yes
+
+# DEFAULTKERNEL specifies the default kernel package type
+DEFAULTKERNEL=kernel-PAE
+EOF
+fi
+
# Uncomment this if you want to use cloud init but suppress the creation
# of an "ec2-user" account. This will, in the absence of further config,
# cause the ssh key from a metadata source to be put in the root account.
diff --git a/generic/fedora-18-i386-minimal.ks b/generic/fedora-18-i386-minimal.ks
index c5fadc6..3a6720a 100644
--- a/generic/fedora-18-i386-minimal.ks
+++ b/generic/fedora-18-i386-minimal.ks
@@ -146,6 +146,19 @@ echo .
echo "Disabling tmpfs for /tmp."
systemctl mask tmp.mount
+# appliance-creator does not make this important file.
+if [ ! -e /etc/sysconfig/kernel ]; then
+echo "Creating /etc/sysconfig/kernel."
+cat <<EOF > /etc/sysconfig/kernel
+# UPDATEDEFAULT specifies if new-kernel-pkg should make
+# new kernels the default
+UPDATEDEFAULT=yes
+
+# DEFAULTKERNEL specifies the default kernel package type
+DEFAULTKERNEL=kernel-PAE
+EOF
+fi
+
echo "Zeroing out empty space."
# This forces the filesystem to reclaim space from deleted files
dd bs=1M if=/dev/zero of=/var/tmp/zeros || :
diff --git a/generic/fedora-18-i386.ks b/generic/fedora-18-i386.ks
index 6076a8a..062f641 100644
--- a/generic/fedora-18-i386.ks
+++ b/generic/fedora-18-i386.ks
@@ -133,6 +133,19 @@ echo .
echo "Disabling tmpfs for /tmp."
systemctl mask tmp.mount
+# appliance-creator does not make this important file.
+if [ ! -e /etc/sysconfig/kernel ]; then
+echo "Creating /etc/sysconfig/kernel."
+cat <<EOF > /etc/sysconfig/kernel
+# UPDATEDEFAULT specifies if new-kernel-pkg should make
+# new kernels the default
+UPDATEDEFAULT=yes
+
+# DEFAULTKERNEL specifies the default kernel package type
+DEFAULTKERNEL=kernel-PAE
+EOF
+fi
+
echo "Zeroing out empty space."
# This forces the filesystem to reclaim space from deleted files
dd bs=1M if=/dev/zero of=/var/tmp/zeros || :
diff --git a/generic/fedora-18-x86_64-cloud.ks b/generic/fedora-18-x86_64-cloud.ks
index 47854fe..36ce1a2 100644
--- a/generic/fedora-18-x86_64-cloud.ks
+++ b/generic/fedora-18-x86_64-cloud.ks
@@ -139,6 +139,19 @@ echo .
echo "Disabling tmpfs for /tmp."
systemctl mask tmp.mount
+# appliance-creator does not make this important file.
+if [ ! -e /etc/sysconfig/kernel ]; then
+echo "Creating /etc/sysconfig/kernel."
+cat <<EOF > /etc/sysconfig/kernel
+# UPDATEDEFAULT specifies if new-kernel-pkg should make
+# new kernels the default
+UPDATEDEFAULT=yes
+
+# DEFAULTKERNEL specifies the default kernel package type
+DEFAULTKERNEL=kernel
+EOF
+fi
+
# Uncomment this if you want to use cloud init but suppress the creation
# of an "ec2-user" account. This will, in the absence of further config,
# cause the ssh key from a metadata source to be put in the root account.
diff --git a/generic/fedora-18-x86_64-minimal.ks b/generic/fedora-18-x86_64-minimal.ks
index 6c08db1..4ae286b 100644
--- a/generic/fedora-18-x86_64-minimal.ks
+++ b/generic/fedora-18-x86_64-minimal.ks
@@ -146,6 +146,19 @@ echo .
echo "Disabling tmpfs for /tmp."
systemctl mask tmp.mount
+# appliance-creator does not make this important file.
+if [ ! -e /etc/sysconfig/kernel ]; then
+echo "Creating /etc/sysconfig/kernel."
+cat <<EOF > /etc/sysconfig/kernel
+# UPDATEDEFAULT specifies if new-kernel-pkg should make
+# new kernels the default
+UPDATEDEFAULT=yes
+
+# DEFAULTKERNEL specifies the default kernel package type
+DEFAULTKERNEL=kernel
+EOF
+fi
+
echo "Zeroing out empty space."
# This forces the filesystem to reclaim space from deleted files
dd bs=1M if=/dev/zero of=/var/tmp/zeros || :
diff --git a/generic/fedora-18-x86_64.ks b/generic/fedora-18-x86_64.ks
index 0854932..651eebf 100644
--- a/generic/fedora-18-x86_64.ks
+++ b/generic/fedora-18-x86_64.ks
@@ -133,6 +133,19 @@ echo .
echo "Disabling tmpfs for /tmp."
systemctl mask tmp.mount
+# appliance-creator does not make this important file.
+if [ ! -e /etc/sysconfig/kernel ]; then
+echo "Creating /etc/sysconfig/kernel."
+cat <<EOF > /etc/sysconfig/kernel
+# UPDATEDEFAULT specifies if new-kernel-pkg should make
+# new kernels the default
+UPDATEDEFAULT=yes
+
+# DEFAULTKERNEL specifies the default kernel package type
+DEFAULTKERNEL=kernel
+EOF
+fi
+
echo "Zeroing out empty space."
# This forces the filesystem to reclaim space from deleted files
dd bs=1M if=/dev/zero of=/var/tmp/zeros || :
10 years, 7 months
