[zones-discuss] Transfer from 'http://pkg.opensolaris.org/release' timed out: timed out.
Hi, I'm just trying to raise awareness on this issue. Folks in the opensolaris-help forum are getting pretty upset because it has not been possible to install a zone for days. See: http://opensolaris.org/jive/thread.jspa?threadID=107149tstart=15 A thread has been started over in opensolaris-discuss as well, but it doesn't seem to have any resolution yet: http://www.opensolaris.org/jive/thread.jspa?threadID=107204tstart=0 Is there a known issue with http://pkg.opensolaris.org/release that's being worked on? Thanks, Brian -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Transfer from 'http://pkg.opensolaris.org/release' timed out: timed out.
I am getting this on the dev tree as well (last 2 days) from an OpenSolaris instance running under VBox 3.0.0 (on Mac OS X). g On 7/6/09 5:28 PM, Brian Leonard wrote: Hi, I'm just trying to raise awareness on this issue. Folks in the opensolaris-help forum are getting pretty upset because it has not been possible to install a zone for days. See: http://opensolaris.org/jive/thread.jspa?threadID=107149tstart=15 A thread has been started over in opensolaris-discuss as well, but it doesn't seem to have any resolution yet: http://www.opensolaris.org/jive/thread.jspa?threadID=107204tstart=0 Is there a known issue with http://pkg.opensolaris.org/release that's being worked on? Thanks, Brian ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Transfer from 'http://pkg.opensolaris.org/release' timed out: timed out.
I had the same problem trying to install Sun Studio last week. I agree that this is a fundamental flaw. Whats kinda funny though is that its not really IPS's fault, nor is it Zone's fault... just an unusual intersection of two assumptions. The only solution currently is a local IPS mirror, but thats not feasible on a small scale. Of course, lets not forget that Zone's already has a rocky relationship with IPS given the non-sparse issue but this may push up the time table. Any guidance as to what the Zones team is doing to resolve the non-sparse IPS problem? benr. Glenn Brunette wrote: I am getting this on the dev tree as well (last 2 days) from an OpenSolaris instance running under VBox 3.0.0 (on Mac OS X). g On 7/6/09 5:28 PM, Brian Leonard wrote: Hi, I'm just trying to raise awareness on this issue. Folks in the opensolaris-help forum are getting pretty upset because it has not been possible to install a zone for days. See: http://opensolaris.org/jive/thread.jspa?threadID=107149tstart=15 A thread has been started over in opensolaris-discuss as well, but it doesn't seem to have any resolution yet: http://www.opensolaris.org/jive/thread.jspa?threadID=107204tstart=0 Is there a known issue with http://pkg.opensolaris.org/release that's being worked on? Thanks, Brian ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Can a non-global zone mount an NFS file system from its own global zone?
Hi John, to clarify, I don't want to mount a root-zone exported filesystem, but, from within the zone, I want to simply leverage the root-zone's automount tree to provide access to each non-global zone to our (seperate) NFS fileservers. I think the technical discussion above gets into the details of this scenario. Hi Niko, I'm glad you feel the same and also want to speak up about about it! (I started a thread in the brandz forum, it's now on the topic of 64bit lx, there are more details there of our environment) Here are the details of my goals: (2 flavors) I would like to build a display-server with 100 users, each with their own personal brandz-Linux zone. Their /pkg or /app space would be a (replicated to the display server) zfs filesystem in the root zone. (lofs this, the simple part). Their /prj or /project space would be the same auto.projects map which all other solaris and linux boxes have. (the heart of this discussion.. I don't want 100 autofs5 daemons running)) the other flavor goes like this: in our LSF farm we generally have 2 kinds of queues (or Job Profiles): large mem (32-64GB) single-core, and multi-core ( =4 core) small-memory 4GB. with a 16 thread, 144GB Nehalem server, we need to have job-slots for both kinds of these; currently with LSF it is impossible for us to have a single machine in both kinds of queues. To go further with my idea, I want to use Solaris resource-controls to help buffer the load, in addition to LSF or Sun Grid Engine to buffer and schedule the jobs before dispatch. You spread those two flavors over a bunch of new modern hardware, and you have a new model which (IMHO) implements virtualization done right. Cheers, Rob -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Can a non-global zone mount an NFS file system from its own global zone?
Should we star a petition? Given that I have a Sun badge I can offer petitioning quite physically ;-) Yes Please! -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Transfer from 'http://pkg.opensolaris.org/release' timed out: timed out.
On Mon 06 Jul 2009 at 02:28PM, Brian Leonard wrote: Hi, I'm just trying to raise awareness on this issue. Folks in the opensolaris-help forum are getting pretty upset because it has not been possible to install a zone for days. See: http://opensolaris.org/jive/thread.jspa?threadID=107149tstart=15 We've had a series of issues with our production infrastructure, some of which should rightly be blamed on me, since my second (third?) job is to run the pkg(5) infrastructure. The pkg(5) team is actively working on these issues. We made some changes on Thursday in response to the original issue the poster mentioned on July 2, and things seemed to be better. The initial problem was created by operator error on my part-- I thought I had applied a critical fix to a python module, but in fact had only done the dry run of the patch. This had the knock-on effect of reintroducing the horrible 408-errors-of-doom problem we've had in the past. For more, see http://defect.opensolaris.org/bz/show_bug.cgi?id=8903. Subsequent to that, we've hit a new round of issues, and we've only partially root caused them. This was all compounded by my absence over the holiday weekend. Finally, we know that people want offline zone installation. We've got a roadmap which points in that direction, and we're trying to get there. Apologies, -dp -- Daniel Price, Solaris Kernel Engineeringhttp://blogs.sun.com/dp ___ zones-discuss mailing list zones-discuss@opensolaris.org
