Marking fix-released per Rob's last comment.
** Changed in: eucalyptus (Ubuntu)
Status: Confirmed => Fix Released
--
After all-in-one setup node-cert.pem and node-pk.pem not found
https://bugs.launchpad.net/bugs/519648
You received this bug notification because you are a member of Ubuntu
I've just done a fresh install on lucid, on one system, and these files
were in place.
--
After all-in-one setup node-cert.pem and node-pk.pem not found
https://bugs.launchpad.net/bugs/519648
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
For the record, I had a all-in-one UEC system running on jaunty in
SYSTEM mode a while ago. I still have my notes somewhere, although I
doubt they would be very applicable to lucid.
--
After all-in-one setup node-cert.pem and node-pk.pem not found
https://bugs.launchpad.net/bugs/519648
You recei
Right, I think it's valid for various NON-PRODUCTION use cases. I
just want to be clear that I don't think we should ever recommend it
for production UEC. It would be up to you to spread that message
appropriately in the classroom, Torsten ;-)
--
After all-in-one setup node-cert.pem and node-pk
Having the option to host a complete UEC on one machine is also relevant
for training. Right now we fall back to one UEC per classroom due to the
two machine requirement, or at most students working in pairs.
--
After all-in-one setup node-cert.pem and node-pk.pem not found
https://bugs.launchpad
Thierry/Mathias-
I've worked with Robert a bit on his setup over the last few weeks. I
must say that I'm impressed/intrigued by the possibility of (even a
minimally supported) all-in-one system, if only for demo and better
community involvement.
I agree that the bug should be wishlist, but if it
Agreed, it would be great if we could fix all the quirks involved in a
single-system setup, so that a single machine would just work. It's just
not part of the target topologies we need to support for 10.04, so I'm
marking it Wishlist.
** Changed in: eucalyptus (Ubuntu)
Importance: Low => Wishl
On Wed, 2010-03-03 at 07:46 +, Thierry Carrez wrote:
> @Robert: this is not a supported topology, upstream always told us NCs
> need to be separated systems (yes, makes testing a little more resource-
> consuming).
>
> ** Changed in: eucalyptus (Ubuntu)
>Status: Incomplete => Invalid
@Robert: this is not a supported topology, upstream always told us NCs
need to be separated systems (yes, makes testing a little more resource-
consuming).
** Changed in: eucalyptus (Ubuntu)
Status: Incomplete => Invalid
--
After all-in-one setup node-cert.pem and node-pk.pem not found
ht
On Tue, 2010-03-02 at 15:26 +, Mathias Gug wrote:
> Hi Robert,
>
> Could you confirm that you installed both the CC *and* the NC on the
> same system?
yes
-Rob
--
After all-in-one setup node-cert.pem and node-pk.pem not found
https://bugs.launchpad.net/bugs/519648
You received this bug not
Hi Robert,
Could you confirm that you installed both the CC *and* the NC on the
same system?
** Changed in: eucalyptus (Ubuntu)
Status: New => Incomplete
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided => Low
--
After all-in-one setup node-cert.pem and node-pk.pem not found
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/38987223/Dependencies.txt
** Attachment added: "EucalyptusAxis2cLog.txt"
http://launchpadlibrarian.net/38987224/EucalyptusAxis2cLog.txt
** Attachment added: "EucalyptusCCLog.txt"
http://launchpadlibrarian.net/38987225
12 matches
Mail list logo
