Re: MunkiWebAdmin2 in early testing

187 views
Skip to first unread message

Gregory Neagle

unread,
Jan 12, 2016, 9:12:00 PM1/12/16
to munk...@googlegroups.com, munki-discuss, munki-w...@googlegroups.com
We’ve already had some contributions and some bug fixes: https://github.com/munki/mwa2/commits/master


Looking for any and all feedback at this point, but here are some specifics that would be helpful:

1) How hard/easy is it to setup the demo? (Answering this one might help others decide whether or not they have time to test MWA2)

2) Usability issues: could you see yourself (or your team) using this to edit manifest and pkginfo files?

3) Performance: acceptable? Too slow? If too slow: how many manifests do you have? How many pkginfo files do you have? What is the connection between your demo/testing machine and the Munki repo?

4) UI issues: is there anything that is confusing or counterintuitive? Are there operations that don’t work as expected?

5) Data loss/munging: are there any operations or workflows that lead to manifest files or pkginfo files being deleted/destroyed/corrupted?

Thanks for any feedback!

-Greg


On Jan 7, 2016, at 4:52 PM, Gregory Neagle <gregn...@mac.com> wrote:

https://github.com/munki/mwa2

MWA2 is a major rethink of web-based administration of Munki.

All reporting has been removed from MWA2 — consider using Sal or MunkiReport-PHP for reporting. Both are excellent.

MWA2 focuses on web-based editing of manifests and pkginfo files.

If you decide to play around with this: please do not point it at a production Munki repo.

-Greg


Gregory Neagle

unread,
Jan 12, 2016, 9:25:42 PM1/12/16
to munk...@googlegroups.com, munki-discuss, munki-w...@googlegroups.com
Another note unless it’s not clear: when using the demo setup you can update to the latest MWA2 code by cd’ing into the mwa2 directory and doing a `git pull`.

-Greg

--
Find related discussion groups here:
https://github.com/munki/munki/wiki/Discussion-Group
---
You received this message because you are subscribed to the Google Groups "munki-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-dev+...@googlegroups.com.
To post to this group, send email to munk...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Joe Wollard

unread,
Jan 13, 2016, 10:26:32 AM1/13/16
to munki-w...@googlegroups.com, munk...@googlegroups.com, munki-discuss

On Jan 12, 2016, at 9:11 PM, Gregory Neagle <gregn...@mac.com> wrote:

We’ve already had some contributions and some bug fixes: https://github.com/munki/mwa2/commits/master


Looking for any and all feedback at this point, but here are some specifics that would be helpful:

1) How hard/easy is it to setup the demo? (Answering this one might help others decide whether or not they have time to test MWA2)

A++ on this. It's basically just a matter of running a script. Compared to the previous version, setting up the demo was a breeze.


2) Usability issues: could you see yourself (or your team) using this to edit manifest and pkginfo files?

Seems useful. Forms/widgets for the basic and intermediate operations and aceEditor for access to the raw plist in the browser seems to cover all the bases nicely.

I noticed some code stubs in there for running makecatalogs in the browser as well - I'm a fan of that eventual functionality ;)


3) Performance: acceptable? Too slow? If too slow: how many manifests do you have? How many pkginfo files do you have? What is the connection between your demo/testing machine and the Munki repo?
N/A


4) UI issues: is there anything that is confusing or counterintuitive? Are there operations that don’t work as expected?

Aesthetics could use some polish (I'll send a PR if I come up with anything), but functionally the UI makes sense to me. 


5) Data loss/munging: are there any operations or workflows that lead to manifest files or pkginfo files being deleted/destroyed/corrupted?

No death or accidental dismemberment of any manifests or pkgsinfo files observed to date.


Thanks for any feedback!

-Greg


On Jan 7, 2016, at 4:52 PM, Gregory Neagle <gregn...@mac.com> wrote:

https://github.com/munki/mwa2

MWA2 is a major rethink of web-based administration of Munki.

All reporting has been removed from MWA2 — consider using Sal or MunkiReport-PHP for reporting. Both are excellent.

MWA2 focuses on web-based editing of manifests and pkginfo files.

If you decide to play around with this: please do not point it at a production Munki repo.

-Greg


--
You received this message because you are subscribed to the Google Groups "MunkiWebAdmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-web-adm...@googlegroups.com.
Visit this group at https://groups.google.com/group/munki-web-admin.

Vaughn Miller

unread,
Jan 13, 2016, 1:29:07 PM1/13/16
to munki-w...@googlegroups.com
1. The demo setup was great, a really painless way to test it out.

2. This looks really useful for our team, the duplicate manifest option is perfect as I have a set of templates to copy when creating a new manifest.  I see having pkgsinfo editing as helpful as well.

It would be useful to have some access control, to allow some users to modify manifests but not pkgsinfo.   I do not know enough django to know if this is easy or hard...

3. Performance was acceptable, my access to my munki repo was over a not so fast smb connection.  My repo is not huge, with a little over 300 manifests and 700+ pkgsinfo files

4. UI - 
 a. On the pkgsinfo screen, it is easy to miss the catalog filter.  This probably just needs a label next to the drop down.
 b. It would be nice to still be able to "follow the link" to included manifests similar to how it works in the current release of  MWA.

5. No damaging effects have shown up so far in my (limited) testing

Vaughn

Gregory Neagle

unread,
Jan 13, 2016, 1:35:05 PM1/13/16
to munki-w...@googlegroups.com
On Jan 13, 2016, at 10:29 AM, Vaughn Miller <vemi...@gmail.com> wrote:

1. The demo setup was great, a really painless way to test it out.

2. This looks really useful for our team, the duplicate manifest option is perfect as I have a set of templates to copy when creating a new manifest.  I see having pkgsinfo editing as helpful as well.

It would be useful to have some access control, to allow some users to modify manifests but not pkgsinfo.   I do not know enough django to know if this is easy or hard…

That capability is already present, just not yet documented. Hint: look at the admin interface. (and I just tested it and see a problem with the admin interface probably caused as I upgraded to Django 1.9…)


3. Performance was acceptable, my access to my munki repo was over a not so fast smb connection.  My repo is not huge, with a little over 300 manifests and 700+ pkgsinfo files

4. UI - 
 a. On the pkgsinfo screen, it is easy to miss the catalog filter.  This probably just needs a label next to the drop down.
 b. It would be nice to still be able to "follow the link" to included manifests similar to how it works in the current release of  MWA.

Agreed. This needs a different UI, though: there’s no special “edit” mode now, unlike the previous MWA.

Gregory Neagle

unread,
Jan 13, 2016, 1:45:33 PM1/13/16
to munki-w...@googlegroups.com
On Jan 13, 2016, at 10:35 AM, Gregory Neagle <gregn...@mac.com> wrote:


On Jan 13, 2016, at 10:29 AM, Vaughn Miller <vemi...@gmail.com> wrote:

1. The demo setup was great, a really painless way to test it out.

2. This looks really useful for our team, the duplicate manifest option is perfect as I have a set of templates to copy when creating a new manifest.  I see having pkgsinfo editing as helpful as well.

It would be useful to have some access control, to allow some users to modify manifests but not pkgsinfo.   I do not know enough django to know if this is easy or hard…

That capability is already present, just not yet documented. Hint: look at the admin interface. (and I just tested it and see a problem with the admin interface probably caused as I upgraded to Django 1.9…)

Not a bug that will affect anyone but me since I had a pre-existing database from before upgrading to Django 1.9 — issue does not affect new installs.

Here’s the relevant bit. In the admin interface (when logged in as the initial superuser), create a new user and then edit their permissions:

Clayton Burlison

unread,
Jan 16, 2016, 6:02:01 PM1/16/16
to MunkiWebAdmin, munk...@googlegroups.com, munki-...@googlegroups.com
1) The demo script has made testing this extremely easy. Thank you.

2) This has been a almost perfect drop in replacement for Joe Wollard's Mandrill and seeing as how I might be the only person running Mandrill in production yes I will be using switching to MWA2 eventually.

3) Performance has been fantastic. ~500 manifests, ~700 pkinfo files. And MWA2 was running on a test server locally and most scans took less than one second. When I mounted over SMB and tested the performance was also quite snappy however when deployed to production it will be running locally on the server hosting my munki repo.  

4) Everything is pretty straight forward. All the operations I have tested work properly. The only UI related note I have is when items with long names or strings appear the line wrapping is less than idea. My manifest is a flat directory structure so no issue there however I have some pkginfo files with long names and long versions which creates horizontal scrolling. 

Mandrill got around this "issue" by having the editor UI in a separate window from the listings. I'm not sure how much effort a change like this might be however it might be beneficial. Another idea would be to make the two window elements, listing and editors, collapsable (not sure the repercussions of that either). If you want to see screen shots of Mandrill without spinning it up for a test: https://www.dropbox.com/sh/apgzwes0rl17u0m/AAB3f7huUKD7OOjoMshJ0UpNa?dl=0 

5) Data loss/munging: Haven't found any yet. Tried most of the daily operations a few times with out issue. I'm kind of curious what would happen with more than on Munki Admin modifying the same file at the same time. However, in my environment that will never be an issue. IE - jane and jim both have the same manifest open for editing. jim clicks save. what happens to jane's save.

--Cheers, Clayton

Gregory Neagle

unread,
Jan 22, 2016, 7:23:29 PM1/22/16
to munk...@googlegroups.com, munki-...@googlegroups.com, munki-w...@googlegroups.com
On Jan 14, 2016, at 9:06 PM, Matt Cahill <cahill...@gmail.com> wrote:


4) UI issues: is there anything that is confusing or counterintuitive? Are there operations that don’t work as expected?

Rendering of the UI elements in the edit panes is a little strange on chrome for me 

Any significant difference from Safari or Firefox?

e.g. Text boxes seem to be as small as possible meaning they have to be resized using the handle to see the contents (single line boxes are ok).

This is normal, if I understand your description properly. You can scroll or resize to view additional contents if desired.

The details pane is larger than the "frame" that contains it meaning you have to scroll horizontally to see the last little bit of the contents.

Same as issue 6? https://github.com/munki/mwa2/issues/6

Text boxes can be resized horizontally which blocks out all titles.

Same as issue 16? https://github.com/munki/mwa2/issues/16

-Greg

Ronald Carter

unread,
Jan 25, 2016, 8:48:20 AM1/25/16
to munki-dev, munki-...@googlegroups.com, munki-w...@googlegroups.com
Mike,

It should be posible you can setup Python and PHP under Windows with IIS I just setup MunkiReport-PHP on IIS. the Apache config will need some work to convert to IIS and should probably stick to SQLite for testing.


On Monday, 25 January 2016 12:39:57 UTC+11, Mike Solin wrote:
I’m really hopeful that someone figures out how to run this on a Windows server (preferably with IIS).  It sounds excellent, and would be really useful in our environment.

Thanks, Greg!


On Sun, Jan 24, 2016 at 5:31 PM, Matt Cahill <cahill...@gmail.com> wrote:

On 23/01/2016, at 1:23 PM, Gregory Neagle <gregn...@mac.com> wrote:


On Jan 14, 2016, at 9:06 PM, Matt Cahill <cahill...@gmail.com> wrote:


4) UI issues: is there anything that is confusing or counterintuitive? Are there operations that don’t work as expected?

Rendering of the UI elements in the edit panes is a little strange on chrome for me 

Any significant difference from Safari or Firefox?

Safari and Chrome render the view very similarly. Firefox seems to be more generous with it’s minimum vertical text box size so the whole thing seems less squished up to the top.


e.g. Text boxes seem to be as small as possible meaning they have to be resized using the handle to see the contents (single line boxes are ok).

This is normal, if I understand your description properly. You can scroll or resize to view additional contents if desired.

This is true and works as described for me. I was just wondering in case there is a way to take up all of the vertical space available in any given browser window?


The details pane is larger than the "frame" that contains it meaning you have to scroll horizontally to see the last little bit of the contents.

Same as issue 6? https://github.com/munki/mwa2/issues/6

Yes issue 6 matches what I saw.


Text boxes can be resized horizontally which blocks out all titles.

Same as issue 16? https://github.com/munki/mwa2/issues/16

Yeah issue 16 matches too.

cheers

Matt


-Greg


--
Find related discussion groups here:
https://github.com/munki/munki/wiki/Discussion-Group
---
You received this message because you are subscribed to a topic in the Google Groups "munki-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/munki-dev/o_cSDHNIOCA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to munki-dev+...@googlegroups.com.

To post to this group, send email to munk...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
Find related discussion groups here:
https://github.com/munki/munki/wiki/Discussion-Group
---
You received this message because you are subscribed to the Google Groups "munki-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-dev+...@googlegroups.com.
To post to this group, send email to munk...@googlegroups.com.

Graham

unread,
Jan 25, 2016, 10:55:59 AM1/25/16
to munki-dev, munki-...@googlegroups.com, munki-w...@googlegroups.com
You could run Docker on your Windows server:

And run MWA2 as a Docker container:

Cheers
Graham

Matt Ware

unread,
Jan 25, 2016, 11:06:57 AM1/25/16
to munki-w...@googlegroups.com
That docker repo appears to be empty

--
You received this message because you are subscribed to the Google Groups "MunkiWebAdmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-web-adm...@googlegroups.com.

Visit this group at https://groups.google.com/group/munki-web-admin.
For more options, visit https://groups.google.com/d/optout.



--
Reply all
Reply to author
Forward
0 new messages