Michal Pryc wrote: > Hello Indiana and Pkg communities, > I have blogged about Imagine, GUI tool for IPS, so you can try it out now: > http://blogs.sun.com/migi/entry/indiana_ips_and_imagine_prototype
Hi Michal, We sync'd up our IPS bits for Ubuntu with those from OpenSolaris and we were able to successfully use Imagine on Ubuntu to install GlassFish and OpenDS. See below for our experience and some recommendations. We'll be trying the same on Windows in the next several days. We're also going to give John Hawk's IpsPkgTool a try on Ubuntu. Thanks! Chris INGREDIENTS =========== Our latest version of the Ubuntu-compatible IPS bits are here: http://wiki.updatecenter.java.net/Wiki.jsp?page=MultiPlatformIPSPrototype We used your Imagine bits from here: http://blogs.sun.com/migi/entry/indiana_ips_and_imagine_prototype STEPS ===== 1) Expand IPS bits for Ubuntu. 2) Expand your Imagine bits. 3) Set PATH to include location of "pkg" CLI. 4) Set PYTHONPATH to location of IPS python scripts. e.g.: export PYTHONPATH=/home/ckamps/ips-demo/ips/usr/lib/python2.4/vendor-packages:$PYTHONPATH 5) Run ./gui/pkgrepo.py to create several new images. One for GlassFish v2 and one for OpenDS. One of these images is set to the "active" image via the "Switch to" button. 6) Run imagine to download and install packages from each of the two repos into separate install images. 7) Follow post install config steps from the update center wiki page listed above. As we formalize packaging of the client side IPS bits, we'll consider including the Imagine tool and we'll simplify the initial set up. We'll be keen to reuse your IPS package form of Imagine in our prototype downloads. FEEDBACK ======== 1) Running gui/pkgrepo.py a) As we've discussed, on non-OpenSolaris platforms, having to run gui/pkgrepo.py prior to running the imagine tool is too awkward. Your use case diagram looks good from our multi-platform perspective. b) pkgrepo.py Script: It would be nice to call this script something else since it's main role is to help manage images rather than repos. However, since users won't need to execute it directly after you make the start up enhancements, this change is not super important to us. c) "Add" dialog of pkgrepo.py: Fields and Field Names of pkgrepo GUI: * Name - it would be useful to rename this field to "Image Name" or name the overall window to "Register Image" or something similar. * Local dir: would be useful to name this field "Image Location" or similar. * Remote url: I found by trial and error that the authority, e.g. "sun.com=", is required to be part of this field in addition to a URL. It would be helpful to do one or more of the following: ** split out the authority into a separate field ** rename the field and/or provide an example where the authority is included Adding an Image: It's not clear from the user interaction that the tool is actually creating a new image and directory (e.g. pkg image-create) or simply trying to register one that already exists. I understand now that the result is the creation of an empty image. Besides, "Remove" doesn't actually delete an image, it simply removes it from imagine's config file. I don't have great guidance here, but it seems awkward that the tool isn't more explicit about the creation process. d) "Image list" window: * It would be very helpful to highlight the active image with a check mark or similar. * We'd rather not have the "Default" image listed if the image doesn't actually exist. The Default entry is noise on non-OpenSolaris platforms. 2) Running imagine Not too much to say here other than great work thus far! It would be nice to make it more explicit to the user that he/she is working with a specific image. Currently, the image name is in parens at the top of the window. That's too subtle when someone is working with more than one image. A much fancier approach would be a View option that presents a navigation tree or list of images on the left. If one image is registered, then the nav column wouldn't be present by default. _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
