Hello, These seem to have been accidentally deleted. I'm trying to find more information. I will keep you posted.
Thanks, Mandar AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement -----Original Message----- From: Krzysztof Opasiak <[email protected]> Sent: Tuesday, August 06, 2019 4:00 AM To: SAWANT, MANDAR <[email protected]> Cc: [email protected]; [email protected]; Samuli Silvius <[email protected]> Subject: Re: [onap-discuss] State of DMaaP AT&T legacy dependencies #dmaap #documentation Dear Mandar Sawant, could you please provide your feedback on below issues? Best regards, Krzysztof Opasiak On 31.07.2019 15:38, Jussi Iho via Lists.Onap.Org wrote: > Hi > Recently I was assigned a task of analyzing DMaaP and its external > dependencies among other things. It was found that DMaaP (and as I > understand it, some other ONAP subsystems as well) depend on a number > of legacy dependencies under AT&T namespace. The issue is, that most > AT&T Github repositories that were presumably supposed to contain the > source codes are currently throwing a 404 error when accessing them. > This issue does not appear to have been yet acknowledged by the > community, and it would be important to do so. > The situation is quite problematic, as there does not appear to be any > documentation on these packages available anywhere either. These > dependencies were apparently internal AT&T projects originally and > then later released as open source, which explains why very little > public information is available on them. The little information about > these packages I've been able to collect has been comprised of > archive.org snapshots, scattered mentions on ONAP documentation and > mailing lists, some disorganized AT&T or other unofficial repositories > still available, limited number of sources.jar packages in Maven > repositories, DMaaP code and Maven pom file analysis, and decompiled sources. > We did consider the chance that perhaps these repositories could have > been moved or renamed, but exhaustive searches have so far come empty. > If they do still exist somewhere online, they have been well hidden. > In the case of DMaaP Message Router, these dependencies were: > *AT&T Java Service Container Framework (com.att.ajsc) > > * > A Spring based framework on top of which DMaaP was apparently designed > to run. It is at least being used for some configuration management > purposes, but we are not sure what the exact capabilities of the AJSC > are and which are actively used. > Unavailable: > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_att_AJ > SC_&d=DwICaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=UIY1jQN-So5boduRQBP94A&m=HmUB2 > uIRq4D9RQuZn5KkotX4WZe1VFTIHDpDdg-yXuU&s=KEhssp81FfE13ndT_XzD9-N11CbCe > R3yNFxdvJHqxiA&e= > Snapshot: > https://urldefense.proofpoint.com/v2/url?u=https-3A__web.archive.org_w > eb_20180627155358_https-3A__github.com_att_AJSC_&d=DwICaQ&c=LFYZ-o9_HU > MeMTSQicvjIg&r=UIY1jQN-So5boduRQBP94A&m=HmUB2uIRq4D9RQuZn5KkotX4WZe1VF > TIHDpDdg-yXuU&s=mBGMMPRYeolNecDopsJ8WkWeH7nh54-Kc-0iXVm7sd8&e= > *Network Service Assurance Library (com.att.nsa) > > * > NSA appears to contain a large number of miscellaneous utilities. We > are not sure where the "definitive" source repository was supposed to > exist, and the package appears in multiple abandoned AT&T repositories > with differing sets of sub-packages inside the namespace. > Available(partially): > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_att_dm > aap-2Dframework_tree_master_CambriaClient_satoolkit_src_main_java_com_ > att_nsa&d=DwICaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=UIY1jQN-So5boduRQBP94A&m=H > mUB2uIRq4D9RQuZn5KkotX4WZe1VFTIHDpDdg-yXuU&s=yy3U5BD37PWFAcxkFt7otWs8H > 62pzGf2CpxKMcAQOQ0&e= > Available(partially): > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_att_NS > ASERVER&d=DwICaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=UIY1jQN-So5boduRQBP94A&m=H > mUB2uIRq4D9RQuZn5KkotX4WZe1VFTIHDpDdg-yXuU&s=RaaOsfnbD9jzX2By75C2wkq8Q > 8sedheq6DEQInAHGMg&e= *Direct Messaging Engine (com.att.aft.dme2) > > * > It is my understanding that a large number of DME references and > related configuration options in DMaaP are not actually being used and > could even be cleaned from the repositories. > > Unavailable: > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_att_DM > E&d=DwICaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=UIY1jQN-So5boduRQBP94A&m=HmUB2uI > Rq4D9RQuZn5KkotX4WZe1VFTIHDpDdg-yXuU&s=mjmyOKZhCFuLgn_onh1pXTFTJ52ckE2 > Rxw1QlFIMVsw&e= > Snapshot: > https://urldefense.proofpoint.com/v2/url?u=https-3A__web.archive.org_w > eb_20180627185025_https-3A__github.com_att_DME&d=DwICaQ&c=LFYZ-o9_HUMe > MTSQicvjIg&r=UIY1jQN-So5boduRQBP94A&m=HmUB2uIRq4D9RQuZn5KkotX4WZe1VFTI > HDpDdg-yXuU&s=DP65hpcqC8q66VkDvEeJnigyPSlzZn9TU0MR8SS36vQ&e= > Unofficial(?): > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_sv8675 > _DME-2D1&d=DwICaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=UIY1jQN-So5boduRQBP94A&m= > HmUB2uIRq4D9RQuZn5KkotX4WZe1VFTIHDpDdg-yXuU&s=ORJACC_gp3vomZzz37BIZWpp > Xpxf6lg_rj3_Blp3AAo&e= > * > Event and Error Logging Framework (com.att.eelf) > > * > EELF is probably not a major issue, as it seems to be used mainly for > simple logging purposes, but it is included here anyway. > > Unavailable: > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_att_EE > LF&d=DwICaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=UIY1jQN-So5boduRQBP94A&m=HmUB2u > IRq4D9RQuZn5KkotX4WZe1VFTIHDpDdg-yXuU&s=OqCDuE0rZGQk_Bj4yf4vZ0LiCk89Hx > MXDReof-sdHu4&e= > Snapshot: > https://urldefense.proofpoint.com/v2/url?u=https-3A__web.archive.org_w > eb_20180612210618_https-3A__github.com_att_EELF&d=DwICaQ&c=LFYZ-o9_HUM > eMTSQicvjIg&r=UIY1jQN-So5boduRQBP94A&m=HmUB2uIRq4D9RQuZn5KkotX4WZe1VFT > IHDpDdg-yXuU&s=uP0zYeVRVNDnl3guDWdutU_mzTO0p1z80nrbHz248Y4&e= > *Some of the raised questions were: > * > 1. Is this truly the case that these source repositories on top of > which DMaaP is built are no longer available anywhere? > 2. Has there ever been proper documentation publicly available on > these packages? > 3. Could we reaffirm if the removal of these AT&T repositories was > intentional (or possibly accidental)? > 4. Would it be realistic to work towards: > a. Reacquiring access to these sources? > b. Attempting to include and them into ONAP project? (where possible) > c. Attempting to refactor the dependencies out? (where possible) d. > Producing at least some documentation on these dependencies? > Thank you. > -- Krzysztof Opasiak Samsung R&D Institute Poland Samsung Electronics -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18449): https://lists.onap.org/g/onap-discuss/message/18449 Mute This Topic: https://lists.onap.org/mt/32681819/21656 Mute #dmaap: https://lists.onap.org/mk?hashtag=dmaap&subid=2740164 Mute #documentation: https://lists.onap.org/mk?hashtag=documentation&subid=2740164 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
