<div dir="ltr">Eventual consistency and time-based historical audit is an interesting combination... This is what the state was 6 days ago, ish... ;)<div><br></div><div>-aslak-</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 27, 2016 at 7:04 AM, Andrew Lee Rubinger <span dir="ltr"><<a href="mailto:alr@redhat.com" target="_blank">alr@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Tue, Sep 27, 2016 at 9:57 AM, Monica Granfield <span dir="ltr"><<a href="mailto:mgranfie@redhat.com" target="_blank">mgranfie@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks all. Yes, persisted work! Great. Transactions... I know ACID is not a priority just putting it out there for consideration while creating the infrastructure...</div></blockquote><div><br></div></span><div>Totally. And in our case I would actually argue that ACID is not only not a priority, it's a poor design decision for work items. Updates to work items aren't, from what I can tell, mission critical enough to warrant the resources and synchronization points involved.</div><div><div class="h5"><div><br></div><div>S,</div><div>ALR</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 27, 2016 at 9:30 AM, Andrew Lee Rubinger <span dir="ltr"><<a href="mailto:alr@redhat.com" target="_blank">alr@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I think we're intermingling concepts. :)</div><div><br></div>To circle this back to multitenancy: yes, anytime a work item is persisted/updated, it should be available to all users system-wide.<div><br></div><div>Transactional integrity does not appear to be a requirement from PM, so something eventually-consistent will do. This means that we take an optimistic approach to subsequent updates and prioritize performance over ACID compliance.<div><br></div><div>Whether that change is pushed to the UI or simply available at the next request is out-of-scope for 6-months requirements from PM.</div><div><br></div><div>S,</div><div>ALR</div></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 27, 2016 at 9:24 AM, Todd Mancini <span dir="ltr"><<a href="mailto:tmancini@redhat.com" target="_blank">tmancini@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I think the only requirement for real-time update is Chat, and, technically, Chat is not part of the 6 month plan (although we are working on it).</div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 27, 2016 at 9:21 AM, Monica Granfield <span dir="ltr"><<a href="mailto:mgranfie@redhat.com" target="_blank">mgranfie@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">How about user status, comments.. any transactions that you would expect to be live or immediate,...Low Pri so long as we account for it, sounds good to me.</div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 27, 2016 at 9:04 AM, Todd Mancini <span dir="ltr"><<a href="mailto:tmancini@redhat.com" target="_blank">tmancini@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>My $0.02.</div><div><br></div><div>1. When we say 'status change', we need to be careful. If I have a WI open for full details and I change basically anything, nothing is persisted until I click Save. (This gives me the option to cancel.) But in other parts of the UI, say, moving a card on a Kanban board from 1 column to another -- that would be an immediate update. I'm not saying anyone is confused by this, but it never hurts to restate it. :)</div><div>2. All WIs have a Status as far as I know, so I don't think we need to talk about "WIs with a status", because that suggests that some do not.</div><div>3. Auto-updating UIs when someone/something changes something -- in general, sure, this is nice to have (say, via WebSockets). But I would call this out as low priority for our first release.</div><span><font color="#888888"><div><br></div><div> -Todd</div></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 27, 2016 at 8:41 AM, Monica Granfield <span dir="ltr"><<a href="mailto:mgranfie@redhat.com" target="_blank">mgranfie@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Sure... if a WI has a status, and the status changes, will it immediately persist and be updated anywhere that WI is viewed. In the past I have run into scenarios about concurrency with objects based on how multi-tenancy is structured. So just want to ask if all data is live or will require updates to see current statuses, states or otherwise...?<div><br></div><div><br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 26, 2016 at 7:08 PM, Andrew Lee Rubinger <span dir="ltr"><<a href="mailto:alr@redhat.com" target="_blank">alr@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><p dir="ltr"></p> <p dir="ltr">On Sep 26, 2016 5:01 PM, "Monica Granfield" <<a href="mailto:mgranfie@redhat.com" target="_blank">mgranfie@redhat.com</a>> wrote:<br> ><br> > One scenario to ask about here... around keeping status in sync with multi-tenants.... Is this something that is good or has been thought about at all?..</p> </span><p dir="ltr">I am not sure I understand the question, Monica. Could you elaborate?</p><div><div> <p dir="ltr">><br> > -Monica<br> ><br> ><br> > On Mon, Sep 26, 2016 at 5:30 AM, Max Rydahl Andersen <<a href="mailto:manderse@redhat.com" target="_blank">manderse@redhat.com</a>> wrote:<br> >><br> >> On 23 Sep 2016, at 0:44, Andrew Lee Rubinger wrote:<br> >><br> >>> I think the question is about more than a URL scheme.<br> >>><br> >>> We've been considering "Project" as our top-level container entity, but<br> >>> there really exists "system" above that.<br> >>><br> >>> By that measure, we can contain in a system:<br> >>><br> >>> * Users<br> >>> * Projects<br> >>><br> >>> ...and then map permissions between users and roles at the project level.<br> >>><br> >>> How does "Organization" map into that?<br> >><br> >><br> >> Good points and I like the notion of "system".<br> >><br> >> The way GitHub and I think VSO does it is that Organizations are owners/containers of projects and users can also be owners.<br> >> Which is why they often share namespace, i.e. cannot have both a user and org called "maxandersen".<br> >><br> >> /max<br> >><br> >>><br> >>> S,<br> >>> ALR<br> >>><br> >>> On Thu, Sep 22, 2016 at 6:37 PM, Todd Mancini <<a href="mailto:tmancini@redhat.com" target="_blank">tmancini@redhat.com</a>> wrote:<br> >>><br> >>>> It's not clear to me what URLs have to do with multi-tenancy. The VSTS<br> >>>> approach (which is actually one "org" per FQDN, but with infinite<br> >>>> projects per org) was chosen for technical reasons, not product<br> >>>> management ones.<br> >>>><br> >>>> So, do you have a technical preference?<br> >>>><br> >>>> The GitHub model seems to work well. But since we also plan to handle<br> >>>> enterprise SSO (via SAML, for example), the Gmail model also works well<br> >>>> (as far as PM is concerned). I'm not married to particular URL schemes.<br> >>>><br> >>>> Sent from my phone, so anticipate hilarious autocorrectsFrom: Max<br> >>>> Rydahl Andersen<br> >>>> Sent: ‎9/‎22/‎2016 6:24 PM<br> >>>> To: Andrew Lee Rubinger<br> >>>> Cc: ALMighty-public<br> >>>> Subject: Re: [almighty] Multitenancy<br> >>>> On 22 Sep 2016, at 21:08, Andrew Lee Rubinger wrote:<br> >>>><br> >>>>> On Thu, Sep 22, 2016 at 3:07 PM, Baiju Muthukadan<br> >>>>> <<a href="mailto:bmuthuka@redhat.com" target="_blank">bmuthuka@redhat.com</a>><br> >>>>> wrote:<br> >>>>><br> >>>>>> Hi,<br> >>>>>><br> >>>>>> ALMighty architecture is going to support Multitenancy, right?<br> >>>>>><br> >>>>> To the bone, yes.<br> >>>><br> >>>><br> >>>> what is unclear though is how the multi tenancy will work.<br> >>>><br> >>>> i.e. is it like github/jira where one instance under one url has many<br> >>>> projects with shared users/orgs<br> >>>> or is it more like VSO where each domain has one project with users<br> >>>> shared across many domains.<br> >>>><br> >>>> Eagerly waiting for some of the "new project" PDD/UX stories to actually<br> >>>> start getting that settled down.<br> >>>><br> >>>> /max<br> >>>><br> >>>>><br> >>>>>> Regards,<br> >>>>>> Baiju M<br> >>>>>><br> >>>>>> ______________________________<wbr>_________________<br> >>>>>> almighty-public mailing list<br> >>>>>> <a href="mailto:almighty-public@redhat.com" target="_blank">almighty-public@redhat.com</a><br> >>>>>> <a href="https://www.redhat.com/mailman/listinfo/almighty-public" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/almighty-public</a><br> >>>>>><br> >>>>>><br> >>>>><br> >>>>> --<br> >>>>> Red Hat Developer Programs Architecture<br> >>>>> @ALRubinger<br> >>>><br> >>>><br> >>>><br> >>>>> ______________________________<wbr>_________________<br> >>>>> almighty-public mailing list<br> >>>>> <a href="mailto:almighty-public@redhat.com" target="_blank">almighty-public@redhat.com</a><br> >>>>> <a href="https://www.redhat.com/mailman/listinfo/almighty-public" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/almighty-public</a><br> >>>><br> >>>><br> >>>><br> >>>> /max<br> >>>> <a href="http://about.me/maxandersen" target="_blank">http://about.me/maxandersen</a><br> >>>><br> >>>> ______________________________<wbr>_________________<br> >>>> almighty-public mailing list<br> >>>> <a href="mailto:almighty-public@redhat.com" target="_blank">almighty-public@redhat.com</a><br> >>>> <a href="https://www.redhat.com/mailman/listinfo/almighty-public" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/almighty-public</a><br> >>>><br> >>><br> >>> -- <br> >>> Red Hat Developer Programs Architecture<br> >>> @ALRubinger<br> >><br> >><br> >><br> >><br> >><br> >> /max<br> >> <a href="http://about.me/maxandersen" target="_blank">http://about.me/maxandersen</a><br> >><br> >> ______________________________<wbr>_________________<br> >> almighty-public mailing list<br> >> <a href="mailto:almighty-public@redhat.com" target="_blank">almighty-public@redhat.com</a><br> >> <a href="https://www.redhat.com/mailman/listinfo/almighty-public" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/almighty-public</a><br> ><br> ></p> </div></div></blockquote></div><br></div> </div></div><br>______________________________<wbr>_________________<br> almighty-public mailing list<br> <a href="mailto:almighty-public@redhat.com" target="_blank">almighty-public@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/almighty-public" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/almighty-public</a><br> <br></blockquote></div><br></div> </div></div></blockquote></div><br></div> </div></div></blockquote></div><br></div> </div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div data-smartmail="gmail_signature"><div dir="ltr">Red Hat Developer Programs Architecture<div>@ALRubinger</div></div></div> </div> </div></div></blockquote></div><br></div> </div></div></blockquote></div></div></div><div><div class="h5"><br><br clear="all"><div><br></div>-- <br><div data-smartmail="gmail_signature"><div dir="ltr">Red Hat Developer Programs Architecture<div>@ALRubinger</div></div></div> </div></div></div></div> <br>______________________________<wbr>_________________<br> almighty-public mailing list<br> <a href="mailto:almighty-public@redhat.com">almighty-public@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/almighty-public" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/almighty-<wbr>public</a><br> <br></blockquote></div><br></div>